Kimi Work by Moonshot AI
Medley vs. Kimi Work
Kimi Work targets knowledge workers with a powerful desktop agent and browser automation. Medley targets founders orchestrating Claude Code across coding and company-building missions.
Paste into Claude Code
Kimi Work brings Moonshot’s Kimi K2.6 model — 1T parameters, 256K context — into a desktop agent aimed at finance, ops, and professional services. It handles coding plus docs and browser tasks with open API key access and Claw Groups for mid-swarm intervention.
Medley overlaps on “more than coding” but differs in architecture: model-agnostic routing across Claude Code, visible mission DAGs, a centralized attention queue, and a project layer designed for AI-native founders on Mac.
What Kimi Work does well
Kimi Work, in beta as of June 2026, packages a frontier-class model into a local-first desktop experience for knowledge workers who need browser automation, document work, and long-horizon tasks — not just diffs.
BYOK is supported, and Claw Groups let you intervene mid-swarm when agents need redirection. For teams already standardized on Kimi’s ecosystem, the integrated agent experience is compelling.
Where Kimi Work stops
There is no true project abstraction — work is session-level and long-horizon, but missions are not decomposed into an editable DAG with dependencies and parallel routing across multiple agent types.
Model support centers on Kimi K2.6 rather than dynamic routing to Claude Code and local models based on task type. The attention model uses Claw Groups, not a single cross-project queue of sign-off decisions.
What Medley does differently
Medley is a Claude Code plugin — multi-agent plans inside the harness you already use, with dynamic routing per sub-task. Missions are first-class objects with targets, budgets, and sign-off gates.
A centralized attention queue is designed to prioritize what needs you across every project. Cost per finished task and decision memory aim to compound your judgment over time.
Key differences
Model routing
Medley routes across Claude Code and more. Kimi Work centers on Kimi K2.6.
Project decomposition
Medley produces editable mission DAGs. Kimi Work runs long sessions without project-level structure.
Attention queue
Medley unifies decisions across projects. Kimi uses Claw Groups within swarms.
Founder ICP
Medley is built for Claude Code power users shipping company-building work.
Full product comparison
| Medley | Kimi Work | |
|---|---|---|
| Product type | Project orchestrator | Desktop AI agent & orchestrator |
| Coding vs. non-coding work | Both — coding and adjacent company-building work | Both — coding + finance, docs, browser |
| Project layer | Project-level — task decomposition across the project | Session-level — long-horizon but no project abstraction |
| Attention queue / human-in-the-loop | Centralized queue — humans pulled in only when needed | Claw Groups for mid-swarm intervention |
| Model access | Uses models you already have in Claude Code | Yes — open API key access |
| Local vs. cloud | Local — Claude Code plugin | Local-first app, cloud model inference |
| Model support | Models you bring into Claude Code (Claude, GPT, Gemini, and more) | Kimi K2.6 (1T param, 256K context) |
| Platform / OS | Mac — desktop app | macOS (Apple Silicon), Windows |
| Pricing & business model | Free — models you already have in Claude Code | Free tier; Moderato $19/mo; Vivace $199/mo |
| Target user / ICP | Founders & power users of Claude Code | Knowledge workers in finance, ops, professional services |
Data as of June 2026. Sources: web research, medley.sh.
Which should you choose?
Choose Kimi Work if
- You want a desktop agent built around Kimi K2.6’s context and capabilities
- Your work is finance, ops, or professional services with browser automation
- You prefer Moonshot’s integrated stack over multi-agent missions in Claude Code
- Claw Groups fit how you intervene in agent swarms
Choose Medley if
- You already run Claude Code and want orchestration across both
- You need mission DAGs, sign-off gates, and cost per task
- You want one attention queue across coding and adjacent company-building missions
- Vendor flexibility and dynamic model routing matter more than a single-model agent
Medley vs. Kimi Work FAQ
- Both do non-coding work — what is the difference?
- Both span coding and non-coding tasks. Medley adds project-level decomposition, multi-agent routing, and a founder-focused attention queue across Claude Code — not a single-model desktop agent.
- Which platforms are supported?
- Kimi Work targets macOS (Apple Silicon) and Windows. Medley is a local-first Mac app in Claude Code — install at medley.sh/install.
- How does pricing compare?
- Medley is free to use — it uses the models you already have access to. Install the Claude Code plugin. Kimi Work offers a free tier plus Moderato ($19/mo) and Vivace ($199/mo) plans on top of model usage.
Orchestrate Claude Code on Mac.
Install Medley — mission control for founders who delegate real work to their agents.
Install MedleyI