Host-readiness checklist
Prepare the repository and development environment before adding a workspace. A good browser interface cannot repair an unknown host setup.
On this page
Start with a known working environment
Use a machine you can inspect and recover independently. Confirm which account will execute development commands, where the repository lives and which credentials it can access.
Choose a non-critical first project. A task that can run builds, tests or scripts inherits the operational risks of those commands.
Before the first real task
Verify access
Confirm your normal SSH or local login workflow and use a dedicated development account where appropriate.
Verify the repository
Inspect the current branch and uncommitted changes. Preserve existing work before creating a new task.
Verify the toolchain
Run the project's documented setup and focused checks through the ordinary host workflow.
Verify runtime authentication
Confirm the intended Codex setup and provider access using the instructions for the installed runtime.
Verify recovery
Maintain a backup and know how to restore the repository and important workspace state.
git rev-parse --show-toplevel
git status --short
git branch --show-current
git worktree listCapacity comes from the workload
Repository size, dependency installation, test processes and parallel sessions all affect CPU, memory and disk use. There is no useful universal VPS size for every agent workflow.
Measure your normal build and test process first. Leave headroom and observe disk growth from caches, worktrees and retained artifacts.
Next step
Use the first-session guide to define a bounded task and a verification plan.