From an empty folder to a signed-off result.
Castiri is a Mac app that runs a team of Claude Code agents in one window. This is the whole process, screen by screen: setting up a project, briefing the team, and running it until every agent has signed off.
Set up the project and the team
Five pages in the New Team assistant, in the style of Xcode's new-project assistant, with Previous and Next along the bottom. Each one takes a minute.
-
Install Castiri and check Claude Code
Castiri needs macOS 15 or later and Claude Code, installed and signed in. Download the app and open it. The Welcome window offers three things: Create New Team, Open Existing Project and Browse Role Library, with your recent projects on the right.
Before any team launches, Castiri checks Claude Code and tells you exactly what to run if it isn't installed, is out of date, or is signed out.
Castiri Version 1.0- Create New Team…Start from a template, a mission, and a brief
- Open Existing Project…Bring a team to a folder you already have
- Browse Role Library…Edit the specialists your teams are made of
-
Choose a template
Eight templates in three groups, Research, Build and Review, plus Blank. Each one fills in a mission, picks a team and gives the agents their first instruction. Pick the closest; everything it chose can be changed on the pages that follow.
- Product Research
- Customer Panel
- Launch Plan
- Design & Build
- Quick Prototype
- Review and Audit
- Executive Review
- Blank
Design & Build. Product, design, architecture, engineering, and security design it and build it, milestone by milestone.
CancelPreviousNext -
Choose where the team works and what it may do
Project: a New Folder, named, with a Git repository if you want one; an Existing Folder; or a Gaitro Project, which gets a draft of its own. Then a permission mode, one for every agent, from Ask before acting to Skip all prompts. Each mode says in plain words what agents may do on this Mac.
Name the team, or leave it blank and Castiri names it after its roles.
ProjectNew FolderExisting FolderGaitro ProjectNametasklistCreate Git repository on my MacPermissions- Ask before actingAgents ask before every file edit and every command.
- Accept file editsAgents edit files in this folder without asking. They ask before running commands.
- Auto modeAgents edit files and run commands without asking, behind Claude Code's safety check.
- Skip all promptsNo prompts and no safety check. Only in a folder you can restore from git.
CancelPreviousNext -
Describe the mission
Three boxes: Goals, Definition of done and Off-limits. Then the Lead's mandate: what the team Lead may decide on your behalf, and what it must bring to you. The template fills in a starting point. The mission is written into CLAUDE.md, so every agent loads it at start.
GoalsDesign and build what the inputs describe, milestone by milestone, with each milestone meeting its acceptance criteria.
Definition of doneEvery must-have in the inputs is designed, built, and verified, and every role has voted Agree in the sign-off table.
Off-limitsPushing to remote branches or deploying. Deleting files outside the project.
The Lead may decidePriorities and order of work, who does what, tie-breaks between teammates, and scope questions the inputs already answer.
Written into CLAUDE.md, so every agent loads it at start. Design & Build filled in a starting point.
-
Assemble the team
The Role Library, grouped by category like System Settings: pick any of the 35 roles, or one you wrote. The chosen team sits along the bottom with each agent's model. One agent is the Lead, your delegate, on the strongest model. Set the model and effort for any role on this team, or apply one setting to everyone.
Each agent is its own Claude Code session, so Castiri shows a cost note once the team is bigger than six.
- Customer
- Product & Engineering
- C-Suite
- Audit & Compliance
- Strategy & Research
- Go-to-Market
- Parker · Product
- Iris · Designer
- Ada · Architecture
- Ezra · Engineering
- Remy · UI Engineer
- Quinn · QA Engineer
Your Team- Parker
- Iris
- Ada
- Ezra
- Vera
- Jo
-
Give the instructions and inputs
Instructions are the first message every agent gets: validate an idea, build a feature list, review a website. Inputs are optional and come in four kinds: a Product Brief, a Feature List, an Idea to Validate or Notes you write in, files and images you attach, and website links, which agents fetch and which show up in Preview. Drop them in.
The footer checks Claude Code one more time. Then Launch Team.
InstructionsInputsRead the inputs and agree on a plan and milestones in the team chat. Iris designs each milestone before it's built; then build it, verify it, and show it in Castiri's Preview.
- Product Brief14 lines
- mock-home.pngImage
- castiri.comWebsite
- Add InputDrop files, images, or links here
Claude Code is readyPreviousLaunch Team
Launch
-
Agree once, then launch
The first launch shows one screen, Before agents start on this Mac. It says what agents can do in the mode you chose; that they run as you, with the same access your Terminal has; where your inputs go, which is to Anthropic through Claude Code under your Claude account, because Castiri has no server; and whose terms apply. Agree and Launch. You see it again only if the text changes.
Castiri then writes the team into the project and starts one Claude Code session per agent, each with a briefing: who is on the team, the mission, the inputs, the files to work in, and the sign-off rules. If Claude Code asks whether to trust the folder, you answer once for every agent.
Written at launchCLAUDE.mdthe mission, in a marked block Castiri ownsdocs/PRD.mdyour Product Briefdocs/INPUTS.mdthe instructions and an index of the inputsdocs/OUTCOMES.mdfindings, scorecard and the Sign-off table.claude/agents/parker.mdone agent file per role, marked as Castiri's.claude/agents/iris.md…
In a Gaitro project these go in a .castiri folder that git ignores, and CLAUDE.md is left alone.
Run the team to sign-off
From here the agents do the work. You watch, answer when a decision is yours, and decide what happens to the result.
-
Watch the team work
One window. The sidebar lists every open project and its agents, each with a status ring: blue working, green idle, orange needs you. The middle shows All Agents, where working agents keep a live terminal and idle ones shrink to tiles, or one agent's terminal, or Preview, where anything the team runs on localhost or writes as HTML appears, or Documents: the outcomes, the instructions and inputs, and the mission.
The inspector on the right holds Team Chat, Mentions and Sign-off. The agents read the inputs, post their first take in the team chat, agree on a plan, split the work and review each other's. A meter on each agent shows the tokens it has used.
-
Answer when it's your call
Agents talk in the team chat and message each other directly. When a decision is yours, the agent asks you, and the question lands in Mentions with a badge: one question, a few options, the agent's recommendation and one reason. The Lead answers teammates' questions that fall inside its mandate and brings you the rest, so you get one question instead of six.
Reply in the thread. The whole team sees your answer unless you send it to one agent only, so everyone works from the same decision.
JoCustomerWhen a task is done, should it hide or stay dimmed in the list?
- Hide
- Dim, hide after a day
- Stay
Recommends dim: people check what they finished today.
Dim, hide after a day. Keep a Show Done toggle.SendEveryone sees your answer·Only send to Jo -
Sign off, then hand off or ship
The team is done when every agent's row in the Sign-off table reads Agree on the same lead idea. Castiri reads the table from the outcomes file and shows who has agreed and, for everyone else, exactly why not: a Block with its objection, a vote still pending, a row that's missing. Once everyone has gone idle it checks in with the holdouts, and you can nudge them yourself.
When the sidebar reads Signed Off, it's your decision: stop the team, hand off to a new team that works from these outcomes, or in a Gaitro project write a one-paragraph summary and Ship. Gaitro runs the project's checks and publishes once they pass. The outcomes file and the Claude Code transcripts stay in the project.
- ParkerProductAgree
- IrisDesignerAgree
- AdaArchitectureAgree
- EzraEngineeringAgree
- VeraSecurityAgree
- JoCustomerAgree
Lead idea: a one-file task list with a Show Done toggle, worded identically on every row.
- Stop Team
- Hand Off to New Team
- Ship Draft #3…
About setting up and running a team.
- What do I need before I start?
- A Mac on macOS 15 or later, Claude Code installed and signed in, and a folder for the project. Castiri checks Claude Code before launch and tells you what to run if it is missing, out of date or signed out.
- Can I use a project I already have?
- Yes. Choose Open Existing Project on the Welcome window, or Existing Folder in the assistant. If the folder already has a brief at docs/PRD.md, Castiri adds it as the Product Brief input.
- What does Castiri write into my project?
- A marked block in CLAUDE.md with the mission, a docs folder with your brief, the instructions and inputs, and the outcomes file, and one agent file per role in .claude/agents. In a Gaitro project, Castiri's files go in a .castiri folder that git ignores and CLAUDE.md is left alone.
- When is the team done?
- When every agent's row in the Sign-off table reads Agree on the same lead idea. Castiri reads the table from the outcomes file, shows who has agreed and why anyone has not, and checks in with the holdouts once everyone has gone idle.
Ten steps. One window.
Open a project, brief the team, and watch the work happen until every agent has signed off.
Download for Mac, freeFree while in beta·macOS 15 or later·Uses your own Claude account through Claude Code