

✓Manus is the general AI agent that bridges minds and actions: it doesn't just think, it delivers results.


Manus is now a Platinum Sponsor of the Godot Foundation. @godotengine is a free, open-source engine built by its community and funded by donations. We're proud to support them. Read the blog here: manus.im/blog/manus-joins-go…







as an engineer myself, mono is game changing. i can't stop talking about it, but if you take away one thing, let it be context visibility. before mono, i built some one-person full-stack features (github export was one!). i'd plan the whole thing with amp in the backend repo first, since you need the endpoints before anything else. then i'd ask amp (so good, btw) for info-gathering prompts, manually open a session in every other repo, paste them in, and dump the answers back into the backend session. then plan, push backend to dev, build the frontend, push again… blah looking back, i was basically the middleman gatekeeping info from an AI that's honestly smarter than 99% of us 🙃 now mono does all of that in one session, with every repo already wired in through git worktrees. it gathers the context itself, so no more me in the middle. and with full context, it catches the sneaky ones: a 1-in-10 case in repo A × a 1-in-10 case in repo B = the 1-in-100 bug you'd never see coming!!

1/ There's no halfway point. Before 2026, we added AI to how we already worked: AI summaries, coding assistants, bots in channels. Each was useful, but nothing was connected. It was the old way of working, with a lot of AI talking over each other. 2/ Context did more than prompts. We built Mono: one entry point to all our repos, plus a manual written for the agent. How the system fits together, how we test and release, and why past decisions were made. Our 7-person mobile team now maintains 4 apps across 2 products. 3/ We closed the loop on bugs. One agent triages a user report and traces it to the change that caused it. The owning engineer hands it to their own agent. A third agent verifies the fix. A person makes the calls in between. Nothing ships without human approval. …… The full post, including what it costs us and what we're building next: manus.im/blog/rebuilding-man…

A year ago, an engineer would read my request, work out what I meant, then write the code. Now our engineers often has 10–20 requests running at once. In September I found my Slack message pasted word for word as an engineer's prompt. What changed when we rebuilt Manus with Manus:

Next Stop: Lisbon. Manus 2.0 is coming to Lisbon. Join the Manus team for a relaxed evening with the local AI community. Meet new people, swap stories about how you’re using AI agents, and share what you’ve been building (or want to build next). RSVP: luma.com/dntnjq3e



