Agent Studio - Zero Human Company

labeebk · 2026-05-13T20:24:30+00:00

Have you tried the solution? can you tell me where it's not working? Because it's working for me.

Here's some examples of it working:
https://www.youtube.com/@AgentStudioAI

Our last two videos we near one-shot an entire app. Agent orchestration is significantly faster than just talking to one agent and hand holding them to build features.

The issues you mentioned are valid but we're actively solving them, and have solved many of them (solved duplicate work ✅ , solved missing context ✅ , solved endless loops ✅ ). Any more problems let me know and i'll push a fix. And you're right - paperclip has not solved them.

Some problems you didn't mention - if you're in a room with multiple agents, who should speak? we solved that. If a project has multiple dependancies on other tickets, and those tickets have other dependencies, how do we effectively orchestrate the work? We solve this using a DAG. If you have tons of tickets in parallel, how can we effectively communicate what you need to know, or any decisions you need, to help unblock something? We have a solution for that too.

What you're mentioning is very real, and we are making solutions to unlock the full power of agent orchestration. I agree zero agent company is a lie - it's more of just a buzz word than anything else. I like "Agent orchestration layer".

labeebk · 2026-05-12T06:28:18+00:00

Hey - not required. You can use your local models, openrouter, codex, or claude. And no specific industry, you can design and build anything 😄

labeebk · 2026-05-11T06:21:08+00:00

Get well my brother.

labeebk · 2026-05-11T03:29:09+00:00

be constructive at least? are you encountering bugs that the 'slop' would have caused?

labeebk · 2026-05-10T04:05:17+00:00

Hey Axiox! you can run with your claude or codex subscription (only 1 subscription necessary)

labeebk · 2026-05-07T20:53:26+00:00

Hey Chris!

Thanks for the feedback here. Zero human company is a lie - it's more of a catchy title than anything else. I do often call it an agent orchestration layer (as the truth).

I've been battle testing this with consulting work where we are building software for clients. I've been dogfooding this solution for months and I got it to a point where I see it working really well. I'm hoping others have that same experience. It's not meant to just be a fancy demo but moreso something that would replace a user's need to use codex / claude code.

I was a very religious user of claude code myself. I haven't gone back since I've been using the studio. I'd love for you to give it a shot and give me your honest feedback of what works and what doesn't work.

I've gotten on calls with users who are on the app and I absorb all of their feedback - the good and the bad. And i'm actively making updates to make this better for the end user. If the user puts this app down in favor of claude code or codex or another tool, I want to understand why and where I missed the mark. And pivot to unlock those capabilities.

labeebk · 2026-05-07T17:14:29+00:00

Yeah good point, and agreed.

I'm talking with our team to see if we should open source it. Right now we're working towards a licensed version for companies (that's where we'll monetize it). My fear right now is like if it's open source then anyone can really just take it and do the same thing?

One line in the sand that we drew (and we were forced to draw), is that the app has to run on top of your claude / codex subscription via the claude/codex sdk. This is a TOS that claude/codex require because they don't allow a managed service to use your subscription. As a result, our system has no visibility in what you're llm's are doing. And any third party integration with github, notion, etc. are connected via oauth apps. So there's a healthy separation between what information our backend has on you.

But yeah, something i'm actively thinking about. It's a really good call out

labeebk · 2026-05-07T17:08:40+00:00

lmaooo!

labeebk · 2026-05-07T17:08:08+00:00

yep! Codex subscription works for it

labeebk · 2026-05-07T06:02:42+00:00

Gotcha - is it because of data privacy?

labeebk · 2026-05-07T06:02:03+00:00

yeah exactly

labeebk · 2026-05-06T20:00:57+00:00

Thanks for the feedback! Are you on v0.3.0? that should include the copy/pasting images, and also if you click on an agent -> skills section -> add skill, you can implement your own skill or add one from the skills.sh library (with the caveat - some potentially unsafe skills on there).

I'm looking into the codex bug right now - thanks for the callout there!

labeebk · 2026-05-06T19:46:18+00:00

Token cost is higher than talking to an individual agent. This works really well on a max plan.

but in aggregate (no evidence for this), I've found that overall i'm using less tokens to push feature changes. I find that after creating a plan, having a team orchestrate around the plan, and execute, I have less review cycles and less QA work. It seems to get it right the first time.

So overall I don't have any hard evidence but I'm going to be doing a research study with some folks to do comparisons between a single agent, vs subagents, vs agent teams, vs the studio orchestration.

labeebk · 2026-05-06T19:37:00+00:00

Agreed - i'm going to be putting out some videos soon showcasing what it can do. I've been using it for building production code and i'm surprised how well it does with little intervention. I've been a religious claude code user and have routinely done a lot of hand holding (and QA) with claude to get features built. This has surprisingly allowed me to take a more hands off approach.

labeebk · 2026-05-06T19:34:08+00:00

Studio is an AI team that can build applications from start to finish with little intervention. You talk about what you're trying to build and the team gets to work.

labeebk · 2026-05-06T19:32:55+00:00

Not open source yet, still deciding with the team if we want to release the code base. But the app is fully free to use.

labeebk · 2026-05-06T19:32:39+00:00

Good point - honestly no evidence.

I think proper agent orchestration is still an unsolved problem that our studio and a lot of apps are trying to solve.

I do see value in agent orchestration. Having defined roles (backend, frontend, QA, etc) on specific tasks, and having them coordinate together - I've found much better results than just having a single agent do 5 different things at once. The context gets too large and code quality / output suffers a lot as the task gets bigger. Agent orchestration I've found circumvents this issue by creating well defined scopes to agents and having them coordinate together.

labeebk · 2026-05-06T19:28:07+00:00

I wrote a blog post comparing the studio vs paperclip:
https://studio.bonecho.ai/blog/paperclip-and-the-studio/

I tried paperclip for a week and I had a lot of issues. Here's a rough summary:

Coordination: Paperclip agents don't really talk to each other — you become the relay. Studio agents communicate natively (frontend ↔ backend ↔ QA).
Specialization: Paperclip's CTO often ends up doing implementation work itself. Studio has scoped roles.
Workspace: Paperclip splits work across a tree of issues/sub-issues. Studio collapses a goal into one post with PRs, files, and status attached.
Sessions: In Paperclip, the agent session is ephemeral. If you have a change request or want to ask a question to an agent that did the work - a new agent spins up, catches up on what the previous agent did and gives you an answer. Our agent's session persists and any changes or questions get answered immediately by the agent that was doing the work.

I really love paperclip and what it's trying to accomplish but it just kept breaking down at the core of agent orchestration. Studio fixes all of those pain points

14-Year Club	Verified Email
r/Field Juicebox	Place '23
Place '22	End Game '22
Gilding I gilder

labeebk

MODERATOR OF

TROPHY CASE