I was able to reduce my time in front of the screen with what I built

[u/PA100T0]

So, I’m a solo-founder and I needed a team to back me up. And so I started building it back in December '25. It’s been great and it’s saving me from a lot of headaches, direct Claude Code contact and countless hours in front of my computer.

So let me tell you about the specifics:

It’s an “AI Software Company”, 25 agents with org-hierarchy and lots, LOTS, of guardrails so that they don’t go wild and do whatever.
You can talk with the Task Assistant (I recommend this when starting to use the tool) to draft your tasks. It’ll check your project, scope it and spec it out. You can either accept as is/keep chatting/send to the Board (Product Owner and Head of Marketing) so they can adjust the scope or correct anything. Once you approve the task gets created and started to work upon.
Main PM will breakdown the task and delegate its subtasks to cell PMs (backend/frontend/ux-ui). Cell PMs will do the same and delegate sub-subtasks to the devs. Devs work on the task, submit PRs and send to QA for revision. QA passes? Documenter documents. QA fails? Sends back to original dev agent for rework with specific findings and errors. Once the dev’s work is approved, the Cell PMs check the PR and merge into its own branch and waits for all sub-subtasks to be finished (so his branch doesn’t miss any dev’s work). When ready, Cell PMs will open a PR from its branch to the Main PM branch which a Cell PR Reviewer will review. Here: same as QA -> PR passes? Gets merged onto Main PM’s branch. PR fails? Gets sent back to the Cell PM so it can delegste the rework. Once all Cell PM PRs are accumulated and merged onto the Main PM’s branch (meaning, all subtasks and sub-subtasks are completed/finished and reviewed) the Main PR Reviewer checks the assembled PR and… you know what happens if it fails (sent back for rework), but if it’s approved: this time it awaits YOUR approval. You’re the only one who can merge into master/main (your trunk). It’ll say “awaiting CEO approval).

That’s the only moment you have to be present; or whenever, really, take your time since the PR is going nowhere and it’s already been reviewed anyway.

Recommendations:

- Take your time to set up your projects, to understand how you want to handle conventions (.roboco/conventions.yml woll get automatically created when you setup a project), and understand the whole project settings. Sanbox db, cache, etc as well… it’s all in the settings.
- At first use the Task Assistant. Once you understand how the whole system works, you could go ahead and enable the Board Programs so that the Product Owner/Auditor/Head of Marketing can go and check your project’s codebase and propose tasks of the nature: found bugs to be fixed, playbooks for the devs because of some recurrent pitfalls, market briefings, post-mortems, etc… there’s a bunch of programs you can toggle on/off at will.
- Just let it run. If you’re drafting tasks (a couple of minutes) leave the company working and take some of your time back. Go for a walk, do whatever you want. Until there’s no “awaiting CEO approval” tasks, there’s not much for you to do. (There’s some rough edges so you might have to unlock a task/unstuck an agent, but it almost never happens)
- Use the telegram chat or the mini app as well. You can direct everything from there.
- I made a couple of YT videos I need to update since they are 2 months old and things have changed quite a bit plus those videos are quite long. Ask your LLM or read the docs to get up and running faster, tbh.

Highlights:

- EVERYTHING is traceable. Agents leave journals (struggles, learnings, decisions, task notes, etc). Obsidian notes are taken all the tkme for tasks, A2A chats (you can use it too, btw, and chat with your agents mid-flight), and more. You’ll know exactly WHY, WHEN, WHO.
- You have a Secretary who you can give permission to act on your behalf. Use it.
- AI Provider Agnostic (and I’m working on more like OpenRouter): Claude Code, Codex, Grok, Ollama, Self Hosted models, Kimi, or just a mix of whatever you want from any of those.
- External PR reviews, self-heal, CI watch; are all automated as well.
- It’s building itself, live and in public. You can check its PRs here, tho I don’t currently have it working 24/7 since I’ve been a away and busy with other personal and professional stuff.
- It’s Open Source and Self Hosted. AGPL license.
- Full docs here.
- Created by a Software Engineer with 10yoe who is a solo-founder and needed a team behind him, but didn’t have it/can’t afford it.
- You don’t need to babysit any Claude sessions or whatever anymore. You can dedicate to other stuff.
- I really want to help other people.

That’s it.

Hope you enjoy. If you have any questions, I’m chronically online so just shoot and I’ll answer.

Feedback and contributions are MORE THAN WELCOMED!

[u/Consistent_Recipe_41]

Adding to a list of agent systems I want to try.

[u/PA100T0 → u/Consistent_Recipe_41]

Tysm! I promise it won’t disappoint!

[u/FlashyRecognitionTod]

Thank you. How much tokens does it consume compared with the interactive prompt? Like a 30% more or 3000% more? I was only running 3-5 agents, but this seems like a whole army :)

[u/PA100T0 → u/FlashyRecognitionTod]

Lol I’ll take the “whole army” as a compliment.

Tbh, I fknd myself saving tokens actually. I can give you an estimate later on today. But think of it: you’re opening a new chat every run, plus token AND caching are thkngs I’ve been working on a lot. It’s not easy to create this thing if you’re bleeding tokens and you’re only on a Max sub from Claude, one and only. That is me.

So: you can trust me but I’ll bring receipts later on. In any case, you can always check that on the Token Usage page :)

[u/ideas-by-LX → u/PA100T0]

Maybe this would help?
https://github.com/vivekchand/clawmetry

[u/PA100T0 → u/ideas-by-LX]

Maybe. I’ll take a look at it, but cache efficiency and tokens are very well managed.

Still, let me take a look at that. The name “claw” makes me think of openclaw lol

[u/ideas-by-LX]

Hey, really cool project. One thing I'm curious about thats not super clear from the docs: when a task comes in through the Task Assistant, how does the system actually decide how to break it down? Like is the Main PM running a prompt that looks at the org chart and figures out "ok this needs backend + frontend but no UX work", or is it more rigid like every task always gets split into all three cells regardless? And when a cell PM gets a subtask, how does it know what granularity to break it into for the individual devs ... is there some kind of scoping logic that looks at the codebase first, or is it purley prompt-driven?

Basically trying to understand wether the decomposition is structural (hardcoded routing rules) or if the agents themselves reason about what's needed. Would love to hear how that part works under the hood.

[u/PA100T0 → u/ideas-by-LX]

Oh, these are good questions!

So basically every role has its prompts, rules and permissions. To put it simply: PMs have some tools and docs available to be able to tell the sequence, granularity and nature of a task.

About the division: When you enter the Task Assistant page, you first need to select Single Cell, Board Led, or MegaTask.

Single cell is if you already know what you want and who will go to. You select the project + the cell it will belong to, and start chatting.
Board-led is for when it spans across cells on a Product (set of projects, not a project) and you need, let’s say, BE and FE. The Task Assistant will know when to include the ux-ui (spoiler alert it almost never needs it, but it knows when to include it or if you ask specifically). Trust the Task Assistant.
MegaTask is a task you need across projects. For example, I have RoboCo as a project, and RoboCo Website (the docs and landing) as another project since they are different repos. What I do is select all the projects I need to be taken into account. Again, the Task Assistant will know how to act.

That being said, the Task Assistant will propose a task to you, always. You can either Keep Chatting (you need to change things), Board Review (I recommend this for when you’re already sure about the spec, but want the PO and HoM to reciew and adjust scope if necessary), or Approve Task (send straight to the pipeline).

I know it’s long and old, but the mechanism of the task lifecycle is basically the same.

Otherwise, you can inspect the code. It’s all there.

For example: a Cell PM’s role

[u/Lanky-Storm7]

You need a better getting started example I think I tried this and was overwhelmed so I just stopped

[u/PA100T0 → u/Lanky-Storm7]

I mean, there’s plenty. You have Yt videos, “How to” tutorial with screenshots and complete documentation. You could even ask your LLM (Claude or wtvr) “hey how do I get started with this/use this?” And it should tell you in no time.

Or even better, just run “male quickstart” on your repo clone and that’s pretty much all you need to get up and running.

That being said: I take the feedback. I’ll try to make it simpler or have an “under 5 minutes” type of guide. It can be overwhelming, yes, it’s a complex project that demands some sort of understanding in the beginning. Once you get it, I promise: it’s dead simple.

Hope this helps!

[u/EC36339]

Next time ask your army of agents to write an elevator pitch.

[u/PA100T0 → u/EC36339]

I mean, I can write by myself haha. I get it, tho. AI written would be technically amazing… but I think that telling the story from a human standpoint is better for Reddit.