/mission for Claude Code

To summarise this launch: project management built directly into AI-assisted software development

Congrats on shipping. It'd be interesting if missions could automatically estimate cost, runtime, and complexity before execution. Is this feature already available?

How Medley handles conflicting outputs when two agents solve the same problem differently?

The BYOK approach is a nice bonus for teams already invested in different model providers. 😊

Wow! It's really interesting that the benchmark improvements came from orchestration rather than a new foundation model.

How would Medley figure which agent comes next versus continuing with the current one?

Fantastic! This solves a pain every Claude Code user eventually runs into projects rarely fit inside a single session anymore. :D

Very cool, congrats on the launch. Is this tool usable / feasible for Pro / Max users who aren't primarily interfacing via the API?

I feel I was too late starting to use Claude Code. But immediately in a week I realised the Claude Code doesn't get the context properly especially if it's a long running task. Hence, I love the idea of orchestrating multiple coding agents instead of manually passing context between them through Medley. I will give it a try.

Spawning a team of agents is the easy part. The hard part is they step on each other and you end up reviewing merge conflicts instead of features. How does /mission handle scope boundaries between agents? That's usually where multi-agent setups fall apart.

This looks like an interesting way to bring more structure to Claude Code workflows. How does it handle situations where the AI takes a different approach than the developer expected?

Bad news. I just used this in Claude to run a longer mission to create outbound emails + find leads. The good: The final result is incredibly good when the mission is complete... most times Claude or other LLMs give you a half finished output and you spend hours of back and forth chatting. Plus I can use this with my existing subscriptions. The bad: Less time with my girlfriend while I spend any time I have using Medley :DThis has been essential to my workflow as a growth member of the team 👏

orchestration is the visible problem, but the one that actually bit us was memory across sessions. splitting work between agents is fine. what breaks is session four not knowing that session two already tried an approach and abandoned it, so it walks cheerfully back into the same dead end.so the bit I'd want is a durable record of what was attempted and rejected, not just what was decided. does the contract cover that, or only the forward-looking guardrails?

the attention queue is the part I'd want to understand before trusting this with anything real. what decides something belongs there - a fixed list of trigger conditions (destructive git ops, spend over some threshold, secrets access) or does the orchestrator itself decide mid-mission what needs a human? the first is auditable, the second has the same problem every self-judging agent has: it only escalates what it's already confident is risky, which isn't the same as catching what actually is. curious which one this is, since the benchmark numbers don't really tell me that

I've been using Medley to build Medley for quite a while now, and it's become one of those tools that's hard to imagine working without.One of the coolest moments was realizing we only needed a skill in the same repo for Medley to start testing and improving itself. I'd hand it an entire feature, and it would break the work down, execute the tasks, test the implementation, and keep making progress on its own. Most of the time, it only came back when it genuinely needed my input.What I enjoyed most was how easy it was to steer. Instead of constantly orchestrating everything, I could jump into just the part that needed my attention while Medley handled the rest. It made building Medley faster, smoother, and honestly a lot more enjoyable.