Pick up where Codex 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 Codex, 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-codex 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. Codex keeps each conversation as a .jsonl file under ~/.codex/sessions/. The first line's payload.cwd is the folder it ran in. 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.
bb finds the repos you've been working in.
Start where Codex left off, so its branch and changes come along.
Choose New thread, then choose the repo and the folder Codex worked in.
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. Codex keeps working while you try bb.
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 Codex; each bb thread reads the one it continues.
Put your setup commands in a .bb-env-setup.sh at the repo root, and list files each worktree needs, like .env, in a .worktreeinclude.
Not on their own. Recreate each one in bb automations: paste its schedule and prompt, and your agent sets it up.
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.
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.
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.