V3Code Cloud

V3Code Cloud is the hosted side of V3Code — and it’s coming.

Note

Status: in development. Cloud is not generally available yet. This page exists so you know what’s planned and can tell the difference between what ships today and what’s still ahead. When it’s ready, full documentation lands here.

The idea

The editor and the terminal are local-first by design: your index, your memory database, and your files stay on your machine. That’s deliberate, and it isn’t changing.

Cloud is about the things a single machine genuinely can’t do on its own — carrying work across devices, and letting a team share what their agents have learned instead of each person starting from zero.

What runs locally today

Everything you need to work already runs without Cloud:

• the agent, sessions, and models in both the editor and the terminal;
• durable memory and the semantic index, stored on your machine;
• the context bridge and all structural code intelligence.

Cloud adds to this. It won’t become a requirement for local work.

Honest status

Team memory transport is the clearest example of where the line sits right now. The terminal queues team handoffs locally, and cloud sync attaches through the signed-in editor. Queued locally is not the same as synced — the product deliberately says so rather than implying work is backed up when it isn’t.

That’s the standard we’re holding Cloud to before it ships: no feature described here as available until it actually is.

Related

• Teams — shared agent work, in active development.
• Account & billing
• Privacy