Project structure
The starter is intentionally small:opencomputer/project.tsdeclares project metadata and agent IDs.opencomputer/agents/<id>/agent.tsdefines one agent.opencomputer/database/migrations/holds ordered SQL migrations for the project’s default database.opencomputer/.env.localoptionally holds ignored development secrets..opencomputer/project.jsonrecords the linked cloud project; the CLI’s build output is cached undernode_modules/.cache/opencomputer/and never lands inopencomputer/.
Create or select the cloud project
The source scaffold and cloud project are separate.opencomputer init writes
local source. Link it to a cloud project with:
binding_required error with the explicit command to run.
You can also link as part of a watched deploy:
.opencomputer/project.json. Run opencomputer link with
an explicit selector again when you intentionally want this source directory
to target another project.
Add another agent
Create a new agent module:opencomputer/project.ts:
development and
production; the playground has a separate agent selector.
Inspect the project
The current project dashboard provides:- Agent playground for creating and resuming test sessions
- Deployments for immutable version history and active aliases
- Sessions created through the dashboard, React client, or API
- Schedules deployed from each agent’s source directory
- Memory for reading, editing and exporting saved agent notes
- Database for inspecting tables, rows and applied migrations, and running read-only queries
- Secrets for write-only project and agent credentials
opencomputer logs to diagnose agent and
outbound-request failures.