Skip to content
V3CodeV3Code
Start here

POPULAR GUIDES

    FROM THE DOCUMENTATION

    Open this guide ↗
    ↑ ↓ select ↵ open esc closeV3Code Docs
    Teamsteams

    Teams

    ↗ View as Markdown

    Shared agent work across a team — what exists today and what's actively being built.

    Teams is where V3Code stops being a single-player tool. It’s in active development, and this page will grow as it lands.

    The idea

    Section titled “The idea”

    One developer with a good agent is faster. A team where every agent shares what the others have learned is a different thing entirely.

    Today, memory is per-machine: your editor and terminal share a memory contract, but that knowledge stops at your laptop. Teams extends that boundary so a team’s agents can hand work to each other with real evidence attached — what changed, what was verified, and what’s still open.

    What ships today

    Section titled “What ships today”

    The terminal already has the local half of this, and you can use it now.

    Team Flight Deck

    Section titled “Team Flight Deck”

    Open the sidebar with Ctrl+X then B and choose the Team tab. It shows the lead session alongside its real child sessions:

    • agent and model identity;
    • busy, retry, or approval state;
    • worktree branch;
    • changed-file count;
    • last update time.

    Clicking an agent opens that session.

    The Worktree Handoff Rail

    Section titled “The Worktree Handoff Rail”

    The rail reports evidence, and it refuses to infer success:

    Label Meaning
    WORKTREE — shared checkout No connected isolated worktree is attached to this session.
    VERIFY — not recorded No captured verification command has finished yet.
    HANDOFF — checkpoint ready The local memory library actually contains that session checkpoint.

    Those are honest states, not errors. A handoff only claims to be ready when the checkpoint really exists.

    Local relay queue

    Section titled “Local relay queue”

    The Memory tab shows team relay counts for queued, sent, received, and retrying handoffs.

    What’s still being built

    Section titled “What’s still being built”
    • Cloud transport. Team handoffs currently attach through the signed-in editor. Full hosted sync arrives with Cloud.
    • Worktree ownership. Workspace and worktree surfaces exist behind an experimental flag. End-to-end isolated agent ownership, safe apply, restore, and handoff aren’t a public promise yet.
    Section titled “Related”