Changelog
New features, improvements, and fixes shipped in each release of Trinity.
v0.1.0-beta
Initial Beta Release
The first public beta of Trinity — a next-generation IDE that plans, executes, reviews, and ships software autonomously through a multi-agent pipeline.
New
- Multi-Agent Execution Pipeline — Stories flow through Analyst → Implementer → Auditor (with simplify loop) → Documenter, each stage run by a dedicated AI agent via the Claude CLI. Automated PR creation, merge, and conflict handling
- Parallel Execution — Run many stories concurrently with a configurable worker pool, each isolated in its own git worktree per repo. Workers know which release they belong to, so release context flows all the way into agent prompts
- Checkpoint & Release Pipeline — Analyst → Audit/Fix loop → Refactor → Audit/Fix loop → Documenter → Knowledge Base consolidation → human gate approval. Multi-perspective quality audits scale with story difficulty
- First-Class Releases — Group PRDs into shippable units with a lifecycle (
created→ready→releasing→released), a dependency DAG, per-repo semver via configurabletag_template+bump_strategy, AI-generated release notes per target, per-release automation overrides, and retry tagging on partial failure. Releases (not PRDs) are Trinity's primary unit — dashboard, stories list, story detail, and Architect all scope by active release, with a release selector that syncs across devices - Architect — Conversational entry point for changing your plan. Classifies requests into
story | epic | phase | prd | roadmapscope, returns amode(add / modify / restructure / new-prd), and surfaces smart signals: release hint, new-target detection, stack implications, PRD size warnings, actionable risk callouts. Every PRD is assigned to a specific release — Architect suggests existing vs. fresh releases or auto-creates the first one. Sessions persist across refreshes and sync across devices - Architect Restructures Mid-Project — When a request implies a structural change, Architect proposes one of
add_target_same_repo | add_target_new_repo | consolidate_to_mono | consolidate_to_turbo. New MCP tools (add_project_repo,update_project_target,merge_project_repos) let it re-home targets, spawn new repos, or collapse a polyrepo — gated by a project-quiet check so it can't race in-flight work - PRD Planning — AI-powered roadmap generation via a 5-phase pipeline (Architect → Story Writer → Dependency Mapper → Target Mapper → Calibrator), producing phases, epics, and stories with dependency graphs and per-story target assignments
- Onboarding Wizard — Multi-step guided project setup: discovery chat, tech-stack refinement, phasing, design preferences, project structure picker, per-repo draft review, section-by-section roadmap review, service API-key setup, and Claude skills configuration. Roadmap generation runs sections in parallel and streams them in as they finish
- Project Import — Bring an existing codebase under Trinity. 7-step flow (scan → review → secrets → docs → skills → save → done) with deep codebase analysis, quality audit, and PRD cross-referencing so already-planned work doesn't clutter the audit checklist. Polyrepo imports show explicit target→repo mapping you can override
- Monorepo / Turborepo / Polyrepo — The structure picker answers one question: how is the project organized in git? Plain-folder monorepo, declared-workspace turborepo (detected via pnpm / turbo / nx / workspaces config), or polyrepo (separate repos at a workspace root). Roadmap and first-PRD prompts shape themselves around the answer
- Polyrepo Execution Gates — Three gate types specific to multi-repo work:
merge_conflict(retry / skip / abort),external_pr_closed(someone closed the PR on GitHub outside Trinity — recreate / skip / abort), andpartial_merge_failed(release tagged some repos but not others — retry the failures or accept a partial release) - Placeholder Audit at Checkpoint + Release — Full-worktree scan with two independent regex families: images (
placeholder.svg,picsum.photos, Lorem ipsum) and contacts (example.com,555-*,John Doe, stale copyright years). Per-family skip toggles, optional agent triage that classifies each hit asleak/fixture/docs/false_positivewith suggested replacements. On-demand scrub available from project settings - Agents Can Raise Their Hand — Any pipeline phase can call the
signal_blockedMCP tool when it genuinely cannot make progress. Thestory_blockedgate carries the escalating phase, a prose explanation, and the list of approaches already tried — so you know exactly what not to suggest - Agents Own Their Repo Docs —
AGENTS.mdis the canonical per-repo agent doc;CLAUDE.mdandGEMINI.mdare thin pointers. Trinity seeds it once, then agents enrich a## Project-specific contextsection as they learn durable facts. Polyrepo projects get a workspace-levelAGENTS.mdthat's DB-backed, rehydrated per worktree, and written through a dedicated MCP tool - Design Guide System — Per-target design references (Web App, Website, Mobile, Desktop, CLI, Library, Extension) loaded automatically by the UX skill based on your project targets
- Knowledge Vault — Database-backed knowledge base (books, chapters, pages) with markdown rendering, tagging, search, and rich zip + PDF exports. Agents query it mid-execution to compound project knowledge over time
- Gotchas Library — Stack-aware common issues and solutions for your languages, frameworks, and tools
- Codebase Map — Living file index with AI-generated descriptions, synced across team members
- Code Viewer — Read-only code browser with syntax highlighting (CodeMirror 6), branch switching, file search (Cmd+P), and virtualized file tree. Uses an isolated bare clone so browsing never interferes with execution
- Dependency Graph — Visual DAG of your stories with saved layouts, highlighting, and fullscreen mode
- Align — Phase-adaptive project health check that evaluates roadmap quality pre-PRD and story/execution health post-PRD. Results auto-save to the vault and stay interactive on reload
- On-Demand Codebase Audit — Scan any codebase for quality gaps, security risks, and improvement opportunities. Audit pages feed directly into Architect via an "Address in Architect" button
- Docker Integration — Per-story Docker Compose isolation with automatic port allocation
- Model Provider Cascade — Settings → AI Models has three selects per tier: harness → provider → model. Switch providers without losing your model choice. Supported: Anthropic (Claude Opus 4.7 default for reasoning, Sonnet + Haiku for lighter tiers), DeepSeek, Ollama, Moonshot (Kimi K2/K2.5/K2.6/K2 Turbo), Z.ai (GLM 4.5/4.6/4.7), Qwen (Coder Plus/Next/Flash, Qwen3 Max, Qwen3.5 Plus/Flash), and automatic fallback between them
- 5-Level Effort Ladder — Every Anthropic call uses the canonical
low | medium | high | xhigh | maxladder. The harness auto-clamps when a model doesn't support the requested level, andai_events.effortrecords the clamped value for accurate cost and latency attribution - Per-Entity Automation Overrides — Override automation and model settings at the story or release level. Cascade is global → team → project → entity → job
- Platform Quality Checks — Preflight checks for TypeScript, iOS, Android, Web, API, CLI, Desktop, Website, Library, and Extension targets
- PDF Reports with Charts — Executive and technical reports with cover pages, visual charts, and polished formatting. Chromium is bundled inside the app for zero-dependency PDF export in production
- Teams — Team scopes with Turso-replicated databases, roles (
owner|manager|member), permission cascade, real-time presence, GitHub repo permission gating, collaborator management (invite / auto-invite / revoke), transfer policies with approval workflows, and business email enforcement - Activity Feed — Global audit trail with filters (project, category, actor), field-level entity history, before/after diffs, provenance badges, and comments
- Seat Sponsorship — Gift subscription seats to other users via token-based accept/decline. Unified
/requestspage surfaces pending invites, sponsorship offers, and project transfer approvals - Multi-Account Sign-In — Stay signed into multiple Trinity accounts at once. Account picker lets you add, switch, and sign out of individual accounts with parallel device-code flows; each account keeps its own warm sync pool and workspace state
- Free Trial — New accounts automatically start a 15-day free trial with full feature access. Trial-expired users see a dedicated screen with a subscribe CTA
- Encrypted Secrets — AES-256-GCM encrypted API key storage per project, account-scoped and synced across devices. Team secrets share a team key. Decryption happens server-side — keys never reach the desktop
- Pluggable Cloud Storage — Managed Trinity Cloud (R2) by default, or bring your own S3-compatible backend (AWS S3, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, MinIO). Credentials cascade from team / global defaults; usage bars show consumption against quota with threshold-based warnings
- Pre-Flight Tool Checks — Contextual verification of git, gh, and claude CLI before project creation and execution. Missing or misconfigured tools surface the exact fix command inline
- Run Page — Splits into Active (running + gated stories with a live pipeline caption showing the current agent) and Queue (pending / ready / awaiting-merge / upcoming). Gate review is a focused modal with per-gate-type bodies — checkpoint gates tab between Overview, Findings, Fixes, Preflight, Notes, and Consolidation
- macOS + Linux Desktop App — Native Tauri v2 app with a sidecar Node.js server, bundled Chromium for PDF export, OS-keyring auth, a custom draggable title bar on macOS, and an execution-aware auto-updater that never interrupts running stories
- Theme System — Six built-in themes: Dark, Light, Trinity Dark (neon-green Matrix aesthetic with monospace font), Trinity Light, Cyber Dark (cyberpunk purple/magenta), Cyber Light — plus system-follow mode
- Help Assistant — Floating chat with context-aware answers from the built-in user guide
- Bug Reports — In-app bug reporting with screenshot attachments, submitted to the admin dashboard
- Built-in User Guide — 27-page guide shipped as markdown, auto-seeded into the knowledge base on startup