spov

Settings

Default model

What a session or job runs on when it names no model of its own.

How to override it

Every launch can still override it: --model on the command line, or the field on the job form.

OpenCode

Sign in with your OpenCode Console account to run OpenCode Go and Zen models. The server holds the sign-in and gives it to your sessions through the credential proxy.

Loading…

Credentials

Tokens your sessions use to reach a forge or a model provider.

Loading…

Routed credentials

Secrets for a private registry or another service, which the sandbox's proxy sets only on the hosts they name. Every session gets them, except one stored to attach only when a launch asks for it. Add one with spov credentials add <name> --host <host> --bearer.

Loading…

Git access

Which repositories a sandbox's git credentials are used on when the launch does not say.

The choices, and what overrides them

Only the ones it starts with, or every repository they reach. Jobs have their own setting, since they run unattended. --git-access and the job form override both.

Job time limit

How long a job may run unattended when it does not say.

What counts, and what overrides it

Time spent steering a job does not count. --max-duration, sandbox.job_max_duration in your config, and the job form override it.

Git identity

Who commits are authored as, which need not be who you sign in as.

Which launches use it

It applies to launches that name no author of their own, which is what the browser starts; spov fly and spov jobs create send your local git config instead. Leave both empty to use the server's own identity.