- Install T3 Code
- Messages and context
- Working with threads
- Permission modes
- Terminal history
- Source control
- Copy local files into new worktrees
- Project settings
- Appearance and themes
- Keyboard shortcuts
- Messaging between threads
- Voice input
- Voice conversations
- Text generation models
- SnapShots
- Visual replies
- Import browser sessions
- Import Claude Code and Codex conversations
- Branch a conversation
- Use T3 Code as your default browser
- Devices
- Usage and limits
- Secrets
- Product usage data
- Remote access
- Guest links
- T3 Connect troubleshooting
- Outside agents (MCP)
- Running in the background
- Updating T3 Code
- Triage an issue
- Provider guides: Codex · Claude · OpenCode · Antigravity · Kiro · Pi · Muse Code · fx
Start with the development runbook and contribution policy.
Internal notes preserve architectural decisions, constraints, and implementation traps that the source alone does not explain. Most code changes do not need an internal documentation update. Follow the documentation rules before adding one.
- Architecture overview
- Glossary
- Connection runtime
- Providers
- Adding a provider
- Pull request file revisions
- Model classification
- Remote environments
- Server updates
- Resource telemetry
- Product analytics
- Environment auth
- T3 Connect
- Assistant citations
- Mobile layout
- Mobile navigation
- Mobile development lifecycle
- Terminal runtime
- Devices
- Voice input