Prizmstack
WorkClientsHow it worksPricingShippedStart a project Shipping since 2019
All work
Our own · Studio OS

Tengu Studio OS

Tengu Studio OS sits under every engagement, and it's built with Claude Code. Any ticket runs in Claude Code with one click: a session in your repo opens the pull request, Claude QA tests its preview, and a person signs off before it ships. Humans decide. Agents carry.

  • Claude Code
  • Tickets
  • QA
  • Slack
  • Calls
  • Weekly demo
Slack threadYOUR CHANNELCallRECAPPEDScreen recordingSHOW, DON'T WRITETenguSTUDIO OSTicket, writtenTRACKED TO LIVECode, reviewedIN YOUR REPOQA on a previewBEFORE IT SHIPSWeekly demoYOU SEE IT RUNNING
Tengu Studio OS194Claude Code pull requests shipped in one week
194Claude Code pull requests merged and live on tengu.work in one week, Oct 19–25
4×the weekly pace over four weeks: 47, 86, 133, then 194
554 of 582pull requests merged into Tengu came from Claude Code sessions
Why we built it

Most of what goes wrong between a client and a studio happens in the gaps: a request made on a call that never becomes a ticket, a Slack message that sinks, a founder who has to chase someone to find out where things stand. And once Claude Code started writing our code, there was a new gap: agent work living in terminals nobody else could see. We built Tengu so every request is a ticket, Claude Code works from the same tickets our people do, and every change is checked before it ships.

What we built
Slack threadYOUR CHANNELCallRECAPPEDScreen recordingSHOW, DON'T WRITETenguSTUDIO OSTicket, writtenTRACKED TO LIVECode, reviewedIN YOUR REPOQA on a previewBEFORE IT SHIPSWeekly demoYOU SEE IT RUNNING
Tengu Studio OS
  1. 01Built with Claude Code, end to end. From September 23, when Tengu's current codebase was started, to October 30, 554 of the 582 pull requests merged into it came from Claude Code sessions; most of the rest are Dependabot bumps. A person merges each one, and main deploys straight to tengu.work.
  2. 02Run in Claude Code on any ticket. One click starts a Claude Code session in the list's own repo with the ticket as the brief. It plans, opens a PR with a live preview, and the ticket follows it from plan to live.
  3. 03When Claude needs a decision, it asks on the ticket. Its ticket turns orange, and whoever answers writes straight back into the session. Nobody hunts through terminals for a run that's stuck.
  4. 04QA with Claude. A second session tests the PR's preview against what the ticket asked for and posts what passed, what failed with steps to reproduce, and what to fix. A person passes it or sends it back.
  5. 05We build exclusively with Claude Code, so the same loop runs on every client account. Ask in Slack, on a call or in a two-minute screen recording and it becomes a ticket, the code lands in the client's own repo, and the Agents tab shows every Claude run across every project.
  6. 06Each week rolls up into a demo of what shipped. Humans decide what's next. Agents carry.
Inside the product
A Tengu ticket, Retry failed payment webhooks, with Run in Claude Code and QA with Claude buttons in its header
A ticket in Tengu. Run in Claude Code starts a session in the list's repo with the ticket as the brief; once its PR is in review, QA with Claude tests it. Shown on sample data.
Claude Code waiting for an answer on a ticket: a question about webhook retries, two options, and a reply box
When Claude needs a decision, it asks on the ticket. The answer goes straight back into its session.
The ticket's Claude pane: the PR's steps from plan to live, Claude's plan, the preview link and the Claude thread
Claude's pane on a ticket: its plan, the PR from draft to live, the preview, and its thread with the team.
A Claude QA report: suggested verdict, action items, checks that passed and failed, and Pass or Send back buttons
Claude QA's report: what passed, what failed with steps, and what to fix, sent back to Claude in one message.
The Agents tab: Claude runs grouped by project, one waiting for an answer and its ticket open beside them
Agents: every Claude run across every project, with the ones waiting on a person first.
What moved

Tengu ships itself through Tengu. Claude Code pull requests merged a week went 47, 86, 133, then 194 across October, each one live on tengu.work once merged. The Run in Claude Code button on our own tickets is the same one on every client's, so how we build Tengu is how we build their products.

Who built it
  • Bryan Gauranodesigned it, and builds it with Claude Code every day
The stack

We build with the latest technologies.

Every product · every engagement

Claude Code · Claude Design · Claude Cowork · Next.js · React Native + Expo · Supabase · Vercel · TypeScript · Tengu Studio OS — every product, every engagement.

Claude Code

All of our development, exclusively. Every product we ship is built with it, Tengu and this site included. People review every change and make every decision.

AI
Claude Design

Screens, prototypes and design systems start in Claude Design, then Claude Code builds them.

Design
Claude Cowork

Everything around the code: research, docs, reports and the studio's day-to-day work, done with Claude.

Operations
Next.js

Every web product we ship. App Router, server components, edge by default.

Web
React Native + Expo

Dosify runs on iOS and Android from one codebase. Ship both from one PR.

Mobile
Supabase

Postgres, auth, realtime and storage. The backend that gets out of the way.

Data
Vercel

Previews on every branch, edge everywhere. This page is running on it right now.

Infra
TypeScript

End to end. The same types in the database, the API and the screen.

Language
Tengu Studio OS

Our own studio OS. Every request becomes a ticket, and every ticket passes review and QA. The studio runs on it.

Ours
The ledger

Shipping since September 2026.

659releases to production
6/6weeks with a release
Fri, Oct 30last release
  1. Fri, Oct 30Tengu15 releases to production
  2. Thu, Oct 29Tengu46 releases to production
  3. Wed, Oct 28Tengu10 releases to production
  4. Tue, Oct 27Tengu26 releases to production
  5. Mon, Oct 26Tengu18 releases to production
The full ledger →
Contact

Yours next?

Tell Bryan what you're building and what's not working. He replies within one business day.

Start a project
Next case · AI platform

Magai

10× · $10k → $100k MRR in two years

Read the case →
Ask the studioAnswers come from our case studies and how we work. For anything else, Bryan.
30 minutes with BryanWhat it is, what's not working, and whether we're the right team.
Times show in your time zone.Open in a new tab