feat: rebrand to Haven Code with Claude Bedrock as default#3
feat: rebrand to Haven Code with Claude Bedrock as default#3dafzthomas merged 3 commits intomainfrom
Conversation
- Rename "T3 Code" → "Haven Code" across all user-facing surfaces (browser title, desktop app name, bundle IDs, git author, error messages, build artifacts, update dialogs) - Change default provider from Codex to Claude Agent (Bedrock) - Hide Codex provider by default; add settings toggle to re-enable - Reorder provider picker: Claude first, Codex hidden behind setting - Keep legacy data dir names and localStorage keys for migration Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
bot
added
size:L
vouch:trusted
The sidebar header used a T3 SVG wordmark + separate "Code" text. Replace with "Haven Code" text wordmark matching the rebrand. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9e46e3f657
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| }> = [ | ||
| { value: "codex", label: "Codex", available: true }, | ||
| { value: "claudeAgent", label: "Claude", available: true }, | ||
| { value: "codex", label: "Codex", available: false }, |
There was a problem hiding this comment.
Setting Codex to available: false here makes the new enableCodexProvider toggle ineffective: AVAILABLE_PROVIDER_OPTIONS is derived by filtering for available === true in ProviderModelPicker, so ChatView can never re-add Codex even when the user enables it in Settings. In practice, users cannot start new Codex threads after turning the feature on, which breaks the advertised gating behavior.
Useful? React with 👍 / 👎.
| const USER_DATA_DIR_NAME = isDevelopment ? "t3code-dev" : "t3code"; | ||
| const APP_DISPLAY_NAME = isDevelopment ? "Haven Code (Dev)" : "Haven Code (Alpha)"; | ||
| const APP_USER_MODEL_ID = "com.haven.havencode"; | ||
| const USER_DATA_DIR_NAME = isDevelopment ? "havencode-dev" : "havencode"; |
There was a problem hiding this comment.
Changing the primary desktop userData directory name to havencode without also checking the prior t3code path causes existing installs to boot against a fresh profile directory. resolveUserDataPath() only falls back to the legacy display-name folder, so users with data under the old normalized folder lose local app state/history visibility after upgrade.
Useful? React with 👍 / 👎.
- State dir default: ~/.haven-code/userdata (was ~/.t3/userdata) - Worktree default: ~/.haven-code/worktrees (was ~/.t3/worktrees) - Desktop state dir follows the same pattern - Fix test expectations for previous rebrand changes - T3CODE_STATE_DIR env var still works as override Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 participant
Summary
enableCodexProvidersetting (default: off) with a toggle in Settings → Codex App ServerTest plan
bun run typecheck— all 7 packages passbun run test— 450 tests passGenerated with Claude Code