​

OpenCode with Xata

​

What OpenCode is good for with Xata

• Local terminal loops where you choose the model and provider.
• Database-aware code changes that use standard Postgres tooling.
• Reproducible branch setup in shell scripts.
• Provider-agnostic experimentation against temporary Xata branches.

​

Quick start

1. Install and initialize the Xata CLI.

curl -fsSL https://xata.io/install.sh | bash
xata auth login
xata init

2. Create a branch for the OpenCode session.

xata branch create --name opencode-task --parent-branch `xata branch get id`

3. Export the Postgres URL.

export DATABASE_URL="$(xata branch url opencode-task)"

4. Start OpenCode from the project directory.

opencode

​

Recommended Xata setup

​

Example prompts

• “Use the database in DATABASE_URL; it is a temporary Xata branch.”
• “Run the migration and test commands against this branch only.”
• “If you need a fresh database state, ask me before deleting or recreating the branch.”
• “Use standard Postgres SQL and avoid Xata-specific assumptions unless the docs say otherwise.”
• “Summarize all database writes before finishing.”

​

Common workflows

​

Provider-agnostic database testing

1. Create a branch for the task.
2. Export DATABASE_URL.
3. Ask OpenCode to implement the change.
4. Run migrations and tests through the project scripts.
5. Delete the branch when the experiment is done.

​

SQL inspection

1. Connect with psql $(xata branch url opencode-task).
2. Ask OpenCode to inspect the schema and failing query.
3. Apply fixes in code or migrations.
4. Re-run the query and tests against the same branch.

​

Tips

• Keep the session scoped to a single branch.
• Use xata branch list and xata branch describe when you need branch state.
• Prefer pooled URLs for high-concurrency local test runners.
• Use API keys only when the agent needs Xata API access.

​

Troubleshooting

​

Related Xata docs

• CLI Reference
• Branch commands
• Postgres extensions
• Scale to Zero