v1.11.0 — Factory foundations: the plumbing

This is the big one. v1.11.0 is us pouring the concrete for the rest of the work on top (namely, multi-mode). A lot of new features landed here as well. Here are the highlights:

The big stuff

Teams, for real (Org → Team → User). Triage Factory now organizes everything around organizations, teams, and people instead of one undifferentiated pile of config. Work routes to the team that owns it, prompts and tracked repos/projects are team-scoped, and Settings splits into Org / Team / User tabs that show you only what your role can touch. Map a Triage Factory team to a GitHub team and the right humans get the right tasks. This enables us to ship an almost identical app as both the on-laptop local mode and cloud-hosted multi-user mode. Local has feature parity with multi by mirroring the same structure with a single entity of each type.

local · sqlite

Your laptop

orgs 1

teams 1

users 1

agents 1

visibility default team

multi · postgres + rls

Hosted

orgs N

teams N

users N

agents 1 per org

visibility default team

Same schema, same code path — local mode is just N = 1.

Your identity and the Factory’s are now separate. The Factory polls and runs autonomous work under its own bot credentials — but the moment you trigger something that writes (a Jira comment, a review, a PR), it acts as you, under your credential, so the audit trail tells the truth. GitHub identity is captured per-user via OAuth, Jira auth is per-user, and if you’re running locally and can’t be bothered, one click reuses your org PAT as your own identity.

Blueprints. Prompts and chains were two ways of saying the same thing, so we merged them into one. A blueprint is a single triggerable unit of work with a durable, portable workspace and clean handoff between steps. Compose them on the canvas, split and merge them, duplicate subgraphs, and rewire them by dragging the arrows.

Composing and rewiring blueprints on the canvas

A run console you can talk to. Agent runs now have a real in-browser home: watch any run live and — the fun part — pause it, send it a message mid-flight, answer its permission prompts, and resume, all without ejecting to a terminal (that escape hatch is gone, because you no longer need it). The board and single-run views got a full liquid-glass redesign while we were in there.

Steering a live run — message, pause, resume

A setup wizard that tries to make the configuration tolerable. First-run is now a guided, step-by-step wizard — GitHub backbone, then trackers (Jira/Linear), then your own identity. The road ahead stays politely hidden until you reach it.

First-run setup, start to finish

Bring your own GitHub App. Connect a GitHub App instead of (or alongside) a personal access token, register a fresh one through a guided flow or import an existing one, and switch between App and PAT without bricking anything. Repo discovery now lists what the App can actually see.

Also new

A grab-bag of smaller wins: the Board and PRs pages got overhauled (plus a cinematic mode for the factory view); PR review comments now carry severity badges and tasks show who a review was requested of; routing got smarter — Jira tasks go to the assignee’s team, GitHub CI/conflict/review tasks to the owning or requested team; repos and Jira projects are now tracked per-team; the review blueprint got a v1 overhaul; a per-project classifier quorum decides what’s worth tracking; integration config moved out of YAML and the keychain into the database; and the event queue is now durable with exactly-once auto-delegation, so a burst of activity no longer quietly eats your tasks.

Fixes

The repo profiler no longer sits out entirely in App-only setups (it was patiently waiting for a PAT that was never coming).
The container image now ships with git and openssh-client, so worktree clones stop failing inside Docker.
The blueprint canvas stopped 404ing when editing a prompt, and the run board now shows live steps instead of a frozen snapshot.
“Continue” in the setup wizard is no longer a test of your patience.
GitHub App registration survives contact with GitHub’s manifest validation and content-security policy.
Evicted the gremlins squatting in the old chains table since the Blueprints migration; they have been relocated to a nice farm upstate.

Quietly under construction

If you read commit logs for fun, you’ll spot a great deal of plumbing in this release for a hosted, multi-tenant Triage Factory — Postgres, per-tenant isolation, sandboxed agent execution, credential proxying, the works. It’s in the box, the hard parts are working, but it’s still missing some polish and testing. We’re landing the foundations now and saving the actual fanfare for when you can sign in and run it. Soon-ish.