Trinity v0.7.0 — PostgreSQL Goes to Production

The big one: PostgreSQL is now the recommended production database. Point one DATABASE_URLat Postgres and the backend + scheduler both switch over — SQLite stays the zero-config default for local dev and evaluation. Migrations are dual-tracked through Alembic. SQLite end-of-support: 2026-09-01.

Read the full write-up in What's New →

Already on SQLite? Migrate cleanly

Migrate with the Trinity Ops Agent's /migrate-to-postgres skill — a gated validate-then-cutover that copies and verifies your data, then cuts over in a short window. Your SQLite file is never written, so rollback is one line.

Also in 0.7.0

• Codex harness MVP— run agents on OpenAI Codex alongside Claude Code and Gemini
• Agent runtime data volumes— declared data paths with snapshot/restore and portable export
• Credential hot-reload rotation— rotate a subscription token without recreating the container
• Execution correctness— fire-and-forget dispatch (a hung turn holds zero backend resource) + status-as-projection
• Security— agent-server inbound auth closes a cross-agent credential-theft surface
• Enterprise— TOTP two-factor auth

36 issues shipped.

Full notes → github.com/abilityai/trinity/blob/v0.7.0/docs/releases/0.7.0.md

GitHub release → github.com/abilityai/trinity/releases/tag/v0.7.0