T3 CodebbSwitch from T3 Code to bb
Pick up where T3 Code left off. Open the task where it was, and your agent reads the old conversation, tells you where things stand, and keeps going.
Pick up a task I was working on in T3 Code, in this folder, and keep going here. First, ask me which work I want to bring over, and suggest the latest conversation you find for this folder. Guide: https://getbb.app/guides/switch-from-t3-code 1. See where the work stands: git log, git status, and git diff against the base branch. If I named a pull request, read it and its comments with gh pr view <url> --comments. 2. Find the conversation where the task was being done, if there is one. T3 Code runs Codex, Claude Code, or OpenCode, so look in ~/.codex/sessions/, ~/.claude/projects/, and OpenCode's ~/.local/share/opencode/ for this folder's path. Pick the latest one for this folder or branch, skipping this conversation and any that only hit errors, and only read it. 3. Write me a short handoff: the goal, what's done, the decisions made, and what's left. Wait for my OK. 4. Continue with what's left. Don't change anything outside this folder, and don't push.
Add your project
bb finds the repos you've been working in.
- Open bb. In setup's Projects step, check the repos you work in, or choose Add a folder that isn't listed.
- Already set up? Open Settings → Projects and choose Add a project.
Create a new thread
Start where T3 Code left off, so its branch and changes come along.
Choose New thread, then choose the repo and the folder T3 Code worked in.
Paste the prompt
- Paste the prompt from and send it. Your agent asks which work you want to bring over, then writes a handoff: the goal, what's done, and what's left. Reply to correct it, or say go.
- Do the same for each task you want to bring over.
Troubleshooting
I can't find my old folder
- Choose Worktree, then Existing worktree. It lists the Git worktrees of the repo you picked, so check that you picked the right repo.
- If the folder isn't a Git worktree, add it as a project in Settings → Projects and start the thread there.
The agent couldn't find the old conversation
- Your agent looks for T3 Code's conversations on this computer. If they were deleted or ran elsewhere, there's nothing to read.
- It then works from the branch or pull request. Tell it what was left to do.
A thread fails right away
- Its agent probably isn't signed in on this computer.
- Sign in to that agent once, then send the thread a message to start it again.
FAQ
Will bb change anything in T3 Code?
No. bb works in your worktrees where they are and doesn't move anything, and archiving a bb thread never deletes a worktree bb didn't create. Bring over one task at a time, whenever you're ready. T3 Code keeps working while you try bb.
What comes along?
Your repos, branches, uncommitted changes, and open pull requests. Claude Code and Codex in bb use the same CLAUDE.md, AGENTS.md, skills, MCP servers, and sign-ins they use now. Your old chats stay in T3 Code; each bb thread reads the one it continues.
Do my setup scripts come along?
Move the scripts that run on worktree creation from t3.json into a .bb-env-setup.sh at the repo root, and list files like .env in a .worktreeinclude.
Do my automations come along?
Not on their own. Recreate each one in bb automations: paste its schedule and prompt, and your agent sets it up.
Does it cost anything? Can I keep my plan?
bb is free and open source, and bb connect is free. bb runs your agents on the subscriptions or API keys you already have. Machines you add cost what they do now.
Which agents work?
Claude Code, Codex, and Pi are built in. Cursor, opencode, and other agents that support the Agent Client Protocol, like Grok Build and Hermes Agent, work once they're installed.
Get more done with the agents you already use
Run more agents at once, see which one needs you, and let them hand work to each other. Free and open source, on the subscriptions you already have.