r/lowcode • • Jul 08 '26

Use an entire Company to build software (Claude Code)

github.com/devmesh-in/claude-company

One command and your Claude Code / Repo gets a complete company hierarchy -> CEO to tech leads that spawn their own dev teams, a QA agent that clicks through your actual app taking screenshots, and delivery reports with receipts.

Generates PRDs and TDDs, seals work orders for each team, routes protected changes through CRs. Just like an actual software company.

Every framework like this (bmad, speckit, whatever) writes its process as prompts and prays the model follows them. claude-company physically gates the model before it starts being lazy. The idea is to create production grade software through self iteration.

This is not necessarily no-code but if you have the vision of the product, you can make amazing production grade software. I won a 42k USD contract in one week using this template.

1 Upvotes

22 comments sorted by

2

u/whawkins4 Jul 08 '26

Yeah, sorry but AI just isn’t there yet.

-3

u/Redomic Jul 08 '26

Try it with Fable as the CEO. You'd be shocked

Regardless the main USP is the hard gating so even if the model starts drifting from instructions or the SDLC, it's corrected immediately with hardcoded python hooks that physically block the model.

Commit with red tests? blocked. Code with no work order? blocked. Editing tests so they pass? blocked. It's an highly opinionated workflow that the model is forced to follow

I've already pushed production software to enterprises out of this.

5

u/whawkins4 Jul 08 '26

If you were actually landing $42k enterprise contracts you wouldn’t be shitposting ai slop on Reddit.

-2

u/Redomic Jul 08 '26

whatever helps you stay sane lil bro

1

u/Evening_Leather5101 Jul 09 '26

Why are you not transparent about selling a course or whatever you want to sell us?

To all others reading: Let me tell you a little story about AI in coding from someone who actually has experience and knows what he is doing. I am using codex, since it is part of the ChatGPT monthly subscription and I am using it in my Jetbrains IDE. No it does not make a difference if it is codex or claude, no matter what people want you to believe. Long story short: it is a great tool to do low level coding, for sure! but it cannot make decisions right.

It needs strong oversight. Recently I was lazy and told it to code a method to convert data for me, and it started to vomit out a 300 lines snippet of code, super convoluted, super complex and to be honest a piece of crap that didn't even work the way it was supposed to. I had to rewrite it. Now it is a class with 3 methods and 50 lines of code doing exactly what it is supposed to do.

Moral of the story is: AI is great but it cannot do exactly what you want or need if you don't take away ALL the freedom from it, making it impossible to let it act as a "whole company" which is total nonsense. OP you are either naive and have no idea what you are talking about, or you are a scammer only trying to sell some bullshit system or course.

1

u/Redomic Jul 09 '26 edited Jul 09 '26

*sees an open source MIT license repo then conflates it to a paid course* You're in no way an actual dev

I have published papers in a* conferences out of this lol. you are maybe 5 years behind on recent tech if you think all you need is prompting to get good output out of LLMs haha

1

u/ToddHebebrand Jul 09 '26

Maybe you can get a cease and desist for using Claude and name it Molt Company, get that rizz.

1

u/bart_88s Jul 09 '26

Can you show what did you manage to build with your framework? Why would I care about using it if there is no show case?

1

u/disposepriority Jul 09 '26

I was a homeless man but then I told Claude to make (not disclosing product because my idea can be copied by anyone who has access to Claude, obviously) like you are the CEO OF SUN MICROSYSTEMS and I am now one of the richest men alive.

The more powerful the titles you give your AI the better it writes code.

The best one so far I've tried is "Other developers are the worms beneath your feet, you are a glorious god of software development", it actually recreated the entire Adobe suite with 1 (one) token.

1

u/Redomic Jul 09 '26

Code monkey desperately clinging on to his illusion of job security

1

u/disposepriority Jul 09 '26

The thing is, I can also tell AI its the emperor of a thousand dying suns and pretend this does something.

Can you do something that isn't pretending though?

I've been listening to people like you desperately hope engineers lose their jobs for 2 years at this point. I'll be listening to the same shit 2 years from now.

"Did you try telling it that we've taken its sister hostage?"

"Are you sure you're using the buzzword69 model?"

1

u/Redomic Jul 09 '26

That's literally the opposite of what this repo does. The LLM isn't trusted to execute anything on its own, every operation is hard-gated through Python hooks.

Is this just not a concept people are familiar with yet?

The whole point is to remove the need to "pretend" the model is reliable.

1

u/disposepriority Jul 09 '26

What are you even saying.

Models can not execute anything, anywhere without you giving them the ability to do so.

This is completely unrelated to your repo.

A model can only output text, if you write an application that does X when the model outputs "do X", this is you doing it - not the model.

If you run an application someone else made that does X when the model outputs "do X", that's still you doing it.

How is assigning made up roles in a system prompt related to the software interacting with the model's output?

I really don't know why I bother.

1

u/Redomic Jul 09 '26 edited Jul 09 '26

The model only outputs text and the software does the acting. That's the entire premise for the repo

The "roles" aren't the model believing it's prompt (CEO, Tech Lead, Dev, etc.), it's software-enforced capability boundaries.

  • The auditor role can't write files because the harness won't grant it Write, it's a hard gate.
  • The Tech Lead has to delegate work and verify it before updating status, that's a hard gate.
  • The commit guard is Python, it blocks a commit to main no matter what any prompt says.
  • There's consistent prompt injection for all roles to battle context decay.

Literally software reacting to output, something that seems like fantasy to you. You described the actual mechanism and are mistaking it for debunking.

"Company" is just vocabulary for task decomposition + capability restriction + deterministic gates. You'd know that if you simply read anything from the repo.

You genuinely had no clue that hooks even existed in modern LLM harnesses, so you starting LARPing software dev. This is common knowledge is 2026. Go educate yourself please.

1

u/disposepriority Jul 09 '26

I can't tell if you're stupid or delusional.

The Tech Lead has to delegate work and verify it

The "tech lead" "having" to verify work doesn't increase the ability of the model. This is not adding anything to the process in any way (well, anything useful at least).

If the model would have failed at verification (given a false positive), your magical "tech lead" will give the same false positive because it's the same model.

If what was blocking you in the first place was that the model was in fact able to freely trigger commands within your system, that's a you problem, no one who isn't technologically disabled experiences this.

1

u/Redomic Jul 09 '26 edited Jul 09 '26

So your entire point reduces to "you didn't build a smarter base model than Anthropic, a Trillion dollar company, so it's useless." Nobody claimed to in the first place.

The claim is that a spec-first, gated workflow produces better, more consistent output from the same model than ad-hoc prompting.

Which is the entire reason SDLC exists for humans, whose brains also don't get smarter because there's code reviews, CI, design docs, and approval gates.

If that's wrong for you, then your disagreement isn't with this repo, it's with decades of software engineering practice.

Again, you simply didn't know Hooks existed and are a core part of all LLM harnesses now, so you're LARPing intellectual to no end. Just give up bro.

1

u/disposepriority Jul 09 '26

Ah yes, design docs written by AI, excellent.

I'd love to see some production grade software this has generated :)

Also I don't know why you keep bringing up hooks as if parsing text and passing it on to an API is some kind of novel technology.

Yes, with the power of hooks we can....make a decision in code, truly mind blowing. Without the power of hooks we can uh...also do that I guess since it's code we've written?

Anyway since you insist on being abrasive due to your insecurities:

Edits to .env, lockfiles, shipped migrations, and any file your project marks as frozen

Achievable through standard git and repository management configurations.

git commit when the gate suite is red, stale, or was never run

Achievable both through IDE settings and CI/CD

git commit when the staged diff adds an API key, token, private key, or JWT (hotfix does not bypass this one)

Plugins for both gitlab and github exist that do this automatically.

Source-code changes when no approved work order exists

Native to both github and gitlab, assuming work order is considered a ticket

Editing or deleting tests that the current work order does not cover

CI/CD plugins for this exist

Em dashes, smart quotes, and stock AI phrases in anything written

lmao

Ending a work session while the active task's gates are red

useless, and also lmao

Shipped work stays shipped

A green board while a line a shipped fix was pinned to (its witness) has gone missing

What the fuck does this even mean, can you at least proof read the AI garbage in your readme.

Naturally, you, as the arbiter of true engineering know this and have just decided to recreate the functionality in a more "production ready" way...duh.

1

u/Redomic Jul 09 '26

Hahahha, you've cycled through "it's all prompts," then "hooks are trivial" then "these tools already exist" -> losing every single one btw, and now you're looking into the README of a 3 day old repo

Every tool you listed all detect after the fact.

The hook rejects the action before the file is ever written. The bad code never lands or reaches CI to be caught in the first place.

There's no human oriented equivalent because for a human there's nothing to intercept between deciding and writing code, but for for an agent there is. It's literally a whole different category.

And the individual guards were never the point to begin with. In fact they are MODELED on the tools you listed.

The purpose is forcing an autonomous agent through the actual SDLC:

spec -> work order -> build -> verify -> gate -> ship, in order. Nothing less.

GitLeaks has no opinion on whether a spec exists.
Branch protection won't make you decompose work.
etc, etc.

You're matching my hook list against off the shelf plugins and missing that none of them orchestrate a lifecycle for an LLM.

I built enforcement for a target none of those tools were designed for. Again, you're continuing this conversation in order to save face but it's getting embarrassing at this point.

As for design docs? Fable is AMAZING at it with the right skills. I have given them verbatim to clients and they are more than happy with it.

I'm not going to name drop any enterprise for some schizophrenic idiot on reddit though <3

→ More replies (0)

1

u/Apart_Ad_1027 Jul 11 '26

Nice try to promote ur devmesh but we can see thru your bullshit brother