Arise vs OpenCode config
The strict ownership boundary between arise.toml and the .arise/opencode/ config directory.
A Arise project's config has two owners, and the boundary is strict.
- Arise owns
arise.tomland.arise/Dockerfile— what a project is, its sandbox, secrets, triggers, apps. - OpenCode owns
.arise/opencode/— how the agent behaves. The platform never reads inside it; it only tells OpenCode where it is.
The config dir is declared via [opencode] config_dir (default .arise/opencode); the agent daemon launches OpenCode with OPENCODE_CONFIG_DIR pointed there.
Ownership table
| Concern | Lives in | Read by |
|---|---|---|
Project metadata (name, description) | arise.toml [project] | Arise |
| Env / secrets spec | arise.toml [env] | Arise |
| Sandbox base image | arise.toml [sandbox] + .arise/Dockerfile | Arise |
| Where the OpenCode config dir lives | arise.toml [opencode] config_dir | Arise |
| Triggers (cron + webhook) | arise.toml [[triggers]] | Arise |
| Apps (experimental) | arise.toml [[apps]] | Arise |
| Agent personas | .arise/opencode/agents/ | OpenCode |
| Skills | .arise/opencode/skills/ | OpenCode |
| Slash commands | .arise/opencode/ (commands) | OpenCode |
| Custom tools | .arise/opencode/ (tools) | OpenCode |
| Plugins | .arise/opencode/ (plugins) | OpenCode |
| MCP servers | .arise/opencode/opencode.jsonc | OpenCode |
| Model / provider config | .arise/opencode/opencode.jsonc | OpenCode |
Rule of thumb
If it describes the project, the sandbox, when work runs, or what gets deployed, it belongs in arise.toml. If it describes how the agent thinks, talks, or acts, it belongs under .arise/opencode/.
Full arise.toml field reference: arise.toml. The .arise/opencode/ directory follows OpenCode's standard layout; see opencode.ai/docs for each primitive.
Where the agent runs
The agent runtime is OpenCode, and Arise runs it in the cloud sandbox — the sandbox agent server launches OpenCode with OPENCODE_CONFIG_DIR set to your config_dir. There is no Arise command that runs the agent on your machine; the CLI is a cloud control plane, not a local runner.
Because .arise/opencode/ uses OpenCode's standard layout, the personas, skills, and tools are portable: install the upstream opencode binary and point its config dir at that folder and it reads the same files.
New files under .arise/opencode/ reach future sandbox sessions only after a change request merges them to main.