Design review of a Mac app that runs teams of AI coding agents
This posting is over three months old and may no longer be active.
Assieme is an open-source Mac app that runs a team of AI coding agents (Claude Code and Codex), each in its own terminal and git branch. It watches the team and fixes common problems on its own: an agent stuck in a loop, the same command refused again and again, agents waking each other for no reason. Merging, deleting work and spending money always stay the person’s decision.
The app works and is released, but it has a design problem: people who open it don’t understand what it does, or why it beats running agents by hand. It was designed by a developer, and it shows. We’d value a designer’s eye on what to improve, and in what order.
Questions are welcome on the forum thread for this job, or as an issue on GitHub.
What we’d like help with
- Look at the main screens (the Team view, Board, Terminals, and starting a new team) and tell us what is unclear, cluttered or missing.
- Suggest how to improve them, most important first. Notes, annotated screenshots or quick sketches are all welcome.
- Tell us what a first-time user needs to see to understand the app.
Helpful experience
- Designing developer tools, or other tools for technical people.
- Product or interaction design for apps with many moving parts.
- Familiarity with macOS conventions.
- Experience with AI coding agents is a bonus, but not required.
What you get
- A real developer tool with active development: your findings will be acted on and shipped.
- Direct work with the maintainer, in short loops.
- Credit in the README and release notes.
Compensation: volunteer for now. We hope to pay for follow-up design work later, but can’t promise it yet.
Use any tool you like: Penpot, Figma, or notes and annotated screenshots. Our own designs live in Paper (paper.design), but you don’t need to use it.
Thank you for reading. We’d be glad to hear from you, even if you only have time for a quick look.
Deliverables
- The main problems you see, most important first, with why each matters.
- Suggestions for fixing them: notes, annotated screenshots or sketches.