What's New in Trinity v0.7.0
Released 2026-06-23
The big one: PostgreSQL is now the recommended production database. Point one DATABASE_URLat Postgres and the backend and scheduler both switch over — SQLite stays the zero-config default for local development and evaluation. Migrations are dual-tracked through Alembic. This release ships 36 issues.
SQLite end-of-support: 2026-09-01. See the release announcement or the full technical notes at docs/releases/0.7.0.md.
Highlights
•PostgreSQL in production — The recommended production database, selected by pointing one
DATABASE_URLat Postgres; the backend and scheduler both switch over. SQLite remains the zero-config default for local development and evaluation, and Postgres migrations are Alembic-tracked (dual-tracked alongside the SQLite runner). Already on SQLite? Migrate with the Trinity Ops Agent's /migrate-to-postgresskill — 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.•OpenAI Codex harness (MVP) — Run agents on OpenAI Codex alongside Claude Code and Gemini CLI. The runtime is chosen via
runtime.type in template.yaml; a Codex agent reads its instructions from AGENTS.md. The Session tab is hidden for Codex (no session resume), but Chat keeps full conversation continuity, and Codex cost is estimated rather than metered exactly. See Agent Runtimes.•Agent runtime data volumes — Declare
data_paths in template.yaml to keep runtime data (SQLite databases, datasets, generated artifacts) out of the git-synced template, then export and import that data on demand as a tar archive to move an agent between Trinity instances. See Agent Data & Portability.•Credential hot-reload rotation — Rotate a subscription token without recreating the container, so in-flight executions keep running. See Subscription Credentials.
•Execution correctness — Fire-and-forget dispatch means a hung turn holds zero backend resource, with execution status modeled as a projection.
•Security — Agent-server inbound authentication closes a cross-agent credential-theft surface.
•Enterprise — TOTP two-factor authentication.
Upgrade Notes
•PostgreSQL is opt-in. Point
DATABASE_URL at Postgres to switch the backend and scheduler over. SQLite continues to work but is end-of-support on 2026-09-01 — plan your migration with the Ops Agent's /migrate-to-postgres skill, which validates before it cuts over and never writes your SQLite file.•Re-login required. As with any update, log in again after the platform restarts, and external tools connected over MCP need to reconnect.