Blog

Insights on AI-powered development, autonomous coding agents, and the future of shipping software.

A device holding encryption keys and plaintext on one side, our server holding only opaque ciphertext on the other, with the zero-knowledge boundary between them

End-to-end encrypted secrets: your keys, your devices

Trinity now ships end-to-end encrypted secrets: keys stay on your devices, our servers hold only ciphertext, and nobody — including us — can read your values.

Lorenzo WynbergJune 10, 20267 min read

Dark cover reading 'Welcome, Codex.' with 'OpenAI's engine joins the family.' beneath, above three engine pills — Claude Code, OpenAI Codex marked new, and OpenCode marked next

Product5 min read

OpenAI Codex joins Trinity's growing engine family

OpenAI Codex joins Claude in Trinity's growing engine family — pick GPT-5.5, GPT-5.4, or GPT-5.4 Mini in Settings, powering every AI action, same framework.

Jun 10, 2026Read more

Dark cover reading "Built on Effect." in white with "Typed errors. Supervised agents." in emerald, beside a code panel showing the Effect AgentResult signature

Engineering10 min read

Why Trinity runs on Effect: typed errors, supervised agents

Trinity runs on Effect across its highest-leverage surfaces. Typed errors and supervised agents make the autonomous pipeline fail loudly, never silently.

Jun 10, 2026Read more

Three projects running concurrently, each pinned to its own git host, transport, and identity — GitHub over SSH, GitLab over HTTPS, and self-hosted Forgejo

Engineering10 min read

Parallel multi-host git: one process, every host

Trinity makes git pluralistic — every project runs against its own host, transport, credential, and identity, all in parallel. Here is how it works.

Jun 9, 2026Read more

A Trinity release card showing three repos — web, api, cli — graded at minor, major, and patch version bumps, with lifecycle pills created, staged, released

Engineering10 min read

Inside Trinity's release pipeline: from merge to tag

How Trinity turns merged stories into a shipped release — grading each repo version bump from real code, walking a staging chain, and tagging every repo on its own.

Jun 7, 2026Read more

Centered title "Harness choice." in white with "Not lock-in." in emerald, above neutral pill chips for Claude Code, Codex CLI, OpenCode, and Local

Company11 min read

Harness choice, not lock-in: Trinity is going multi-harness

Anthropic's June 15 programmatic-usage cap is a harness-layer change, not a model one. Here's why Trinity treats the harness as the real unit of portability — and how Claude Code, Codex CLI, and OpenCode all earn their place.

May 16, 2026Read more

Trinity's stack before and after — Next.js + React + standalone server on the left, Solid + Vite + Hono on the right, with bundle, launch, and memory deltas underneath

Engineering10 min read

How Solid + Vite + Hono cut Trinity's cold launch 37%

We rewrote Trinity's desktop from Next.js + React to Solid + Vite + Hono. Cold launch is 37% faster, the bundle is 33% smaller, idle memory is 19% lower.

May 3, 2026Read more

Diagram showing the evolution from a simple bash loop to Trinity's multi-agent release pipeline

Engineering8 min read

The Ralph Wiggum Loop, evolved

The bash loop proved AI agents can ship code. Trinity evolves it into a multi-agent pipeline with parallel execution, quality gates, and compound knowledge.

Mar 27, 2026Read more