OpenCode vs Prime Agent

OpenCode

Runs with no key or account on free OpenCode Zen models. Most permissions default to allow, and SECURITY.md says the permission system is not a sandbox.

Prime Agent

Budgets for turns, tokens and time bound an autonomous run, and sessions survive a closed terminal through a supervising daemon. Model-written Python and shell commands run with the user's rights, with no approval step and no sandbox, and the Rust build on the main branch ships only as nightly betas.

OpenCode

1. Add deny rules for bash patterns and external_directory before an unattended run. Most tools default to allow
2. Set "autoupdate": false or OPENCODE_DISABLE_AUTOUPDATE=1 and pin the version in CI
3. Configure a provider key. With none, prompts go to free Zen models that may train on them
4. Set OPENCODE_SERVER_PASSWORD before opencode serve. Without it the server runs unauthenticated
5. Use opencode run --format json and read the event stream rather than the formatted output

Prime Agent

1. Run it in a disposable clone, container or VM. It executes model-written Python and shell commands with the user's rights and asks nothing first
2. Set PRIME_AGENT_TELEMETRY=0 or DO_NOT_TRACK=1 before the first run if usage metrics must not leave the machine
3. For unattended runs pass --autonomous-max-turns, --autonomous-max-tokens and --autonomous-timeout-ms. Reaching a limit does not mean the task succeeded
4. Headless use is -p with --mode json per the argument parser. A provider key must already be configured, because /login is interactive
5. The -t/--tools, -nt/--no-tools and -nbt/--no-builtin-tools flags were removed and now fail as unknown options