Skip to main content

Maggy

Autonomous AI engineering command center.

Chat with your codebases across Claude, Codex, and Kimi — with semantic routing that picks the cheapest model that can handle the task.

Key Features

  • Semantic Routing — local Ollama model rates task complexity and type, routes to Local/Kimi/Codex/Claude accordingly
  • Interactive Chat — SSE streaming, session resume, ghost-text suggestions (Tab to accept)
  • Inline Model Forcing — type "use claude" in any message to override routing
  • Parallel Execution — Polyphony container orchestration for complex tasks (blast>=7)
  • AI-prioritized Tasks — ranks open issues by urgency + OKR alignment
  • One-click Execute — TDD pipeline with iCPG context enrichment
  • Council PR Review — a multi-model council reviews a GitHub PR from the dashboard: deterministic mega-PR chunking, a static gate (tsc/ruff) as ground truth, an adversarial refute pass to kill false positives, and extensible per-language skills (Python/TS/Go/Rust/Java/C#/Ruby/PHP — drop in more). pip install maggy-harness[review]
  • Competitor Intelligence — auto-discovered competitors, daily AI briefing
  • Engram Memory — persistent cross-session memory with amnesia diagnostics

Quick Start

pip install maggy-harness    # or: pipx install maggy-harness
maggy bootstrap              # installs skills, hooks, ~/bin model wrappers, plugins

# Pull the local model (optional but recommended)
ollama pull qwen3-coder:30b-a3b

# Configure (optional — Maggy runs in local mode without keys)
export GITHUB_TOKEN=ghp_...
export ANTHROPIC_API_KEY=sk-ant-...

# Launch
maggy              # interactive REPL (auto-detects project)
maggy serve        # web dashboard at localhost:8080
maggy chat api     # chat with a specific project

Or install from source for development:

cd maggy
pip install -e .

Or from inside Claude Code:

/maggy-init   # interactive setup wizard
/maggy        # launch dashboard

How Routing Works

Every message gets a semantic blast score (1-10), then routes to the cheapest capable model:

Blast Tier Models
1-3 Low Local (Qwen3-Coder), Kimi
4-6 Medium Codex, Kimi
7-10 High Claude, Codex

The router learns from outcomes — successful tasks reinforce the routing decision.

Tests

cd maggy
python3 -m pytest tests/ -x -q

887 tests, target coverage >= 80%.

Docs

License

MIT

Metadata

Release files for maggy-harness 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for maggy-harness 0.2.1
File Size Uploaded
maggy_harness-0.2.1.tar.gz 540.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for maggy-harness 0.2.1
File Interpreter ABI Platform
maggy_harness-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / maggy_harness-0.2.1.tar.gz

Download URL maggy_harness-0.2.1.tar.gz
Size 540.0 kB
Tags Source
SHA-256 checksum
How to use checksums
55ca3f38812e7c7dcec8cf9dadb0b4760bd5d62b915a64754f4815567d916ffd
BLAKE2b-256 checksum
How to use checksums
d1b8f97cf2461f526045f0171fa69af17cc0cd48c653880316b0f0c1082963c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 21, 2026.

Transparency log

Release files / maggy_harness-0.2.1-py3-none-any.whl

Download URL maggy_harness-0.2.1-py3-none-any.whl
Size 510.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bd16b95aa2efb882ad77f9fd670b95e43df5eab2b32a388c3b1e40abdc0b49a7
BLAKE2b-256 checksum
How to use checksums
e046f64553b44e16c92d3ec744b368d5b68d948834a8434b7e762170a72872ea
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 21, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page