Expertise on purpose.
Discover professional roles and focused skills for the work in front of you. Read what helps the next decision instead of loading an entire catalog.
Explore rolesOPEN SOURCE · LOCAL FIRST
Give your agents
a working
practice.
The right expertise. The right tools. A result you can inspect. Mirket brings a shared working practice to Codex and Claude.
One Rust CLI. Runs on your machine. MIT licensed.
WORKBENCH / 001EXAMPLE
THE TASK
Build an interface.
Verify what actually ships.
01
Choose the expertise
Frontend engineering · Design QA
02
Scope the tools
Workspace · Browserless · Pixel inspection
03
Close the loop
Render → inspect → refine
A SMALL PLACE TO START
$ mirket setup
$ mirket
doctor
Your project. Your host. Your permissions.
WORKS WHERE YOU WORKCodex DesktopClaude Desktop CodemacOS ARM64 · Linux x64 · Windows x64
01 / THE APPROACH
Less context by default.
More judgment where it counts.
Start with the deliverable. Bring in useful expertise, assign a bounded toolset, and check the actual outcome.
Tools with boundaries.
Mirket-owned workers receive tools for declared task needs. A role title cannot expand access. Your host continues to control permissions.
Read the routing contractEvidence over ceremony.
Inspect the saved file, working screen or system effect. Use durable task records when continuity helps, and keep the workflow you already trust.
See verification02 / TASK-SHAPED ROUTING
Different work.
Different demands.
Models are discovered from authenticated runtime targets. Task complexity and tool requirements establish the capability floor.
The router governs Mirket-owned workers. Native host agents retain their own execution boundary.
EXPLORE A ROUTEILLUSTRATIVE
T3
Creative & architectural
Layout decisions and multi-step visual reasoning require the architectural tier.
- Expertise
- Frontend engineering + interface design
- Tool scope
- Workspace, Browserless, image inspection
- Verification
- Render the screen and inspect its pixels
A capability floor, not a fixed model list. Ambiguity resolves upward.
03 / THE DESIGN WORKSPACE
One connected toolchain.
From tokens to proof.
The optional design package connects eleven purpose-built tools through a shared workspace. Each has a defined job.
01
Define
Style Dictionary
Canonical tokens → CSS, themes, Typst & Penpot
02
Compose
Satori + resvg · Browserless · Penpot MCP
Static cards, full DOM screens & editable canvases
03
Explain
Kroki · HyperFrames · Typst
Diagrams, motion, reports & slide decks
04
Prepare
ComfyUI · imgproxy · SVGO
Generate rasters, process images & optimize vectors
05
Verify
Odiff · Browserless
Compare pixels and inspect the rendered resultThe core CLI needs no background service. The optional design stack uses a managed local runtime and additional memory. Package guide ↗
04 / GET STARTED
Make it part
of your practice.
Download the executable for your platform, place it on your PATH, then choose your clients in setup.
Full installation guide
Download for macOS
Rename the file to mirket, make it executable, and add its directory to PATH.
mirket setup
mirket doctorRelease notes & checksums ↗ MIT license
A few useful details.
Does Mirket replace Codex or Claude?
No. It installs shared guidance and MCP connections into supported hosts. The host retains permissions, authentication and its session lifecycle.
Do I need the entire design stack?
No. The Rust CLI and expertise catalog work independently. Select the design package only when you need its rendering, canvas and media tools.
Does local mean inference stays on my device?
The harness and its state run locally. Model inference uses your authenticated targets, which may be remote providers or a local daemon. Your provider's data and billing policies still apply.
Can I use it with an existing project?
Yes. Mirket can adopt an existing project and install selected expertise. Setup preserves unrelated client configuration and checks managed files for drift. Your project's instructions govern the work.