Coding studio
Your next coding project, shipped
Someday is now. AI Agents and Agentic Assistants for your work: the Coder writes the change, and the Product owner keeps the backlog clear. You give the final go.
The next change
Code and a patch for review
- The repositories you ship
- The tickets that repeat
- Where you give the final go
Nothing is sent or shipped unless you asked for it or approved it, and money always asks.
GitHub, Slack, and Linear come with the studio. You set the goal, the team does the work, and a merge waits for you.
A closer look
An idea goes in.
Real work comes out.
Code and a patch for review. Explore how the pieces fit.
Illustrated workflow
02 / The team works
The team works
The assistants take the goal, use the ready prompts and skills, and do the work in the tools you connected.
How it works
From a goal to a result.
- 01
Set a goal
You say what done looks like: a ticket, a client, a deadline, or a draft.
- 02
The team works
The assistants take the goal, use the ready prompts and skills, and do the work in the tools you connected.
- 03
You approve the risky step
Anything that sends, publishes, ships, or charges waits for your Approve. Approve a kind of step once and that assistant remembers it, but money always asks.
- 04
You get the result
A draft pull request, with the tests and the summary, ready for your review.
Example
Send the release notes to three customers
It sends to people, so it asks first.
The team
You, and the assistants.
You
You set the goal and approve the merges, deploys, and messages that leave the studio.
Coder
Makes a checklist plan for a larger change and ticks off each step, writes the code and the tests, and opens the pull request on its own. A merge waits for your Approve.
Product owner
Turns a vague request into an issue, ranks the backlog, and writes the status update.
Integrations
The tools it starts with.
- GitHub
- GitLab
- Slack
- Linear
- Telegram
Built in
What your assistants can use.
Its own computer
Each assistant works on its own computer in StellarFirm cloud, set up with the tools its job needs, and hands you the files.
Roles you make yourself
Name a role we don't ship, say what it does and give it any of our skills or your own. Comes with Ultra and enterprise.
A running app beside the chat
The Coder starts the app it built and shows it live next to the chat, so you can click through it yourself.
Keep going until it is done
Say what done looks like and the Coder keeps going, up to ten more rounds, until the goal is met. /stop ends it.
Long jobs in the background
A big job starts at once and runs in pieces in the background, streaming back as it goes. You can stop it any time, and sends and spending still ask.
Follows up on its pull requests
Switch it on for a Coder and it takes on failing checks, merge conflicts and review comments on its own pull requests. Merges and replies still ask you.
It asks only when it matters
Assistants make and change things on their own and ask before they send, publish or delete. Approve a kind of step once and that assistant stops asking; money always asks.
Pages and documents beside the chat
A page, chart, table, document or picture an assistant makes opens beside the chat, so you can check it while the work goes on.
Marketplace
Expert teams for this work.
Coming soon
Example
Quantum software team
Quantum algorithms and the code to run them, with a Coder, a Scientist and a second Coder who reviews.
Ready to use
Prompts and skills.
Skills
- Draft a pull request from the top ticket
- Write tests
- Review a pull request
- Fix CI
- Draft an issue
Ready prompts
Pick up the top ticket and open a draft pull request.
Plan this feature as a checklist, tick each step off as you go, and open the pull request when the tests pass.
Review the open pull request and list what I should ask for.
Questions
Before you join.
Start with your first assistant.
Leave your email. Invites go out every day until 27 October, and we'll write when your spot is ready.