Onboard in a live session, not a setup doc.
Drop a new engineer into a warm drive that already has the repo, the dependencies, and a running environment, and let them follow a teammate through the codebase in a live session. Day one is building, not configuring.
Day one used to be a setup doc, a dozen installs, and a broken local build.Now it is a warm drive and a teammate to follow in a live session.
What a new engineer gets on day one.
No machine to configure and no stale doc to decode. A warm drive, a live session to join, and an agent that already knows the repo. Every line below is running in production today.
A drive that is ready, not a laptop to configure
A cloud drive stays warm with the repo cloned, dependencies installed, and the environment running. A new engineer opens it from any device and starts. No local setup, and idle time is never billed.
Join from any browser, or the CLI
Open the drive in a browser, or log in once from the terminal with a device code and attach to the drive by name. The stock OpenCode CLI attaches unchanged, so a new hire uses whatever they are comfortable with.
Learn the codebase live, not from a doc
Presence shows who is in the session. Follow a teammate's view to watch where they look and what they prompt, ask questions in the in-session chat overlay, and see the same shared, auto-reloading localhost preview they do.
The agent already knows the repo
The repo was read into the session long before the new hire arrived, and it stays warm. A new engineer prompts the same agent everyone else does and gets answers grounded in the real code, with no context to load of their own.
Set up the drive once, onboard everyone from it.
The repo is read into the drive once and kept warm for everyone who joins. The drive holds up to 100 teammates, so a new hire joins the same drive your team already works in, in the same live session, with the same agent. Sessions push to your real git, and access is controlled per session, so you decide what a new engineer can see and join.
Onboarding, answered
Does a new hire have to set up a local environment first?
No. The drive is a cloud workspace that stays warm with the repo, the dependencies, and a running environment ready. A new engineer opens it in the browser, or attaches from the CLI, and starts in a working environment. There is nothing to install locally, and the drive sleeps when idle, so idle time is never billed.
How does following a teammate work?
Several people share one live session on one running filesystem and terminal. Presence shows who is in the session, and you can follow a teammate to see their view as they move through the codebase and prompt the agent. There is an in-session chat overlay for questions, and the localhost preview is shared and auto-reloading, so a new hire sees exactly what a teammate sees.
Can I keep parts of onboarding private?
Yes. Access is controlled per session. Keep a session private to you, share it with named teammates, or open it to the whole drive. A mentor can run a private session and invite the new engineer by name, or open a shared session for the whole team to join.
Onboard your next hire in a live session.
Launch a warm drive with the repo and environment ready, invite a new engineer, and let them follow a teammate from the first hour. Open it in the browser, or attach from the OpenCode CLI.