Launching today
Crew44
Turn coding agents into specialist teams
44 followers
Turn coding agents into specialist teams
44 followers
Crew44 โ a crew of specialist AI agents in one local-first workspace. Each role on the model that wins its job, with memory and skills that compound. No account, free, open source.
Crew44
Hey Product Hunt ๐
Iโm Zander, maker of Crew44.
Crew44 started as my own messy workaround for a problem I kept running into: I was using multiple AI coding agents every day โ Claude Code, Codex, Gemini, Cursor โ but they all felt like separate contractors who had never met each other.
Every session meant re-explaining the repo, copying context between tools, repeating project conventions, and manually deciding which agent should do what.
So I built Crew44: a local-first command center that turns the AI coding agents already installed on your machine into one coordinated crew.
You can create specialists like Cofounder, Engineer, Product Lead, Designer, or Reviewer, etc. bind each one to the runtime/model that fits the job, and let them work in a shared project workspace with memory, skills, and structured handoffs.
A few things I cared a lot about while building it:
* Local-first by default
* No account, no subscription
* MIT licensed
* Works with the tools you already use instead of trying to replace them
The goal is not to build โone AI agent to rule them all.โ, but to make the agents you already trust work more like a real team.
Crew44 is still early, and Iโd genuinely love feedback from people who use multiple coding agents in their workflow. Try (and modify it) for free: https://github.com/getcrew44/crew44
Thanks for checking it out. Iโll be here answering questions ๐
AISA AI Skills Test
the model-per-role approach is the right call. most teams default to one model for everything which is like hiring one person and expecting them to be good at architecture, testing, and docs. curious how the memory compounding works across sessions though โ does each agent retain context from previous projects or start fresh?
Crew44
@ozandagย exactly โ thatโs the mental model I had too. One model for everything feels convenient at first, but the roles start to matter once the work gets more complex.
For memory, Crew44 is project-scoped by default. In my experience, project-scoped memory tends to stay more relevant, can be updated more frequently, and is much easier to automate safely. So each project gets its own local storage first.
Cross-project memory is also supported if you want it โ all sessions are locally stored so it's easy to maintain a global memory file and query specific details.
Congrats on the launch @zanderforge.
The demo looks really promising. This honestly hits a pain I feel constantly as a solo builder. Also genuinely appreciate the local-first, MIT and no-account approach. In this space, that combination is rare, and it builds trust before I've even tried the product.
I'm planning to plug Crew44 into one of my current projects and will come back with honest feedback once I've used it on a real workflow.
Wishing you lots of momentum from here ๐
Crew44
@anandkparmarย Thanks so much Anand โ really appreciate it.
Solo builders were exactly who I had in mind for Crew44. Would love to hear what feels useful or awkward once you try it on a real project. Cheers!