Smart · Efficient · Interesting AI Coding Assistant

HagiCode turns ideas into shipped work with OpenSpec workflows, multi-agent parallel execution, and Hero Dungeon battle reports that keep AI coding visible, structured, and enjoyable.

🌐 Visit Website · 🖥️ Desktop · 🐳 Container · 📚 Product Overview

简体中文

---

What HagiCode is built for

HagiCode is an AI coding product for teams and individual developers who want more than a single chat box. It combines proposal-driven workflows, parallel agent execution, and memorable product feedback so complex work stays understandable from idea to archive.

• Smart - OpenSpec gives each change a clear path through idea, proposal, review, implementation, testing, and archive.
• Efficient - Claude Code, Codex, and other CLI agents can run across multiple agents and instances in parallel, so fixes, reviews, and delivery keep moving together.
• Interesting - Hero Dungeon rosters, battle reports, and visual workspaces turn long-running AI collaboration into something easier to follow and more rewarding to use.

Visual Tour

The gallery below uses product-owned assets stored in repos/site, so the README can show the current product directly on GitHub. Instead of relying on a single hero image, it walks through the real proposal flow, fast execution mode, skill safety surfaces, Hero identity, and desktop controls.

Proposal stages at a glance
_{UI screenshot. Follow one proposal from optimization through archive in a single nine-stage timeline.}

Inline review and annotations
_{UI screenshot. Add focused inline comments before sending precise feedback back to AI.}

Execution result with code diff
_{UI screenshot. Inspect the applied diff immediately after execution finishes.}

Normal session execution result
_{UI screenshot. Use a quick session when a task does not need the full proposal flow.}

Skill trust and managed command
_{UI screenshot. Confirm the install source, trust status, and exact managed command for every skill.}

Hero highlight and product personality
_{Product visual. Hero Dungeon themes and battle reports give long-running AI sessions a recognizable identity.}

Desktop start service control
_{UI screenshot. Start or monitor the local HagiCode service from the desktop dashboard.}

Desktop version management
_{UI screenshot. Switch packages, dependencies, and release tracks from the desktop version center.}

Why teams use it

• Proposal-driven by default - Scope, tasks, and archive history stay connected, so AI work remains reviewable.
• Designed for parallel throughput - Real-time token tracking, multi-agent workspaces, and execution views are built for multiple streams at once.
• Easy to remember and revisit - Hero Dungeon and Hero Battle reports add narrative, momentum, and clearer status feedback.

Getting Started

Start with the official entry points:

• hagicode.com for the full homepage experience
• Desktop to install the local app
• Container for the self-hosted deployment path
• Product Overview for the documentation entry

Run the site locally from repos/site:

npm install
npm run dev
npm run build
npm run preview

The dev server runs on http://localhost:31264 by default. For contributor-focused details, start with AGENTS.md and CLAUDE.md.

Build and deployment notes

This repository now focuses on building the static site and related content. Deployment now follows the active hosting pipeline rather than a legacy repo-local static-site flow.

• Build output is generated into dist/ with npm run build.
• Homepage activity metrics are consumed at runtime from https://index.hagicode.com/activity-metrics.json.
• Desktop package fallback data lives on the index site at https://index.hagicode.com/desktop/history/ and https://index.hagicode.com/desktop/index.json.
• If runtime data looks wrong or stale, inspect the index repository and its deployment chain before adding local copies here.

Homepage activity metrics

The homepage activity metrics module is a runtime consumer of the canonical JSON hosted by the index site:

• Source: https://index.hagicode.com/activity-metrics.json
• Single source of truth: repos/index generates and publishes the only metrics asset that repos/site is allowed to consume
• Ownership: the data is produced and published from repos/index, not from repos/site
• Failure mode: if the remote asset is unavailable, the homepage keeps the existing empty-state fallback instead of breaking the page
• Maintenance boundary: if the metrics look wrong or stale, investigate the index repository and index deployment first instead of re-adding a local refresh script or JSON copy here

Desktop version fallback

• The homepage install entry and the standalone Desktop page both consume runtime package data instead of maintaining a site-local release list
• When package loading reaches terminal failure, the canonical fallback target is https://index.hagicode.com/desktop/history/
• repos/index remains a referenced dependency only; treat https://index.hagicode.com/desktop/history/ and https://index.hagicode.com/desktop/index.json as the stable fallback surface
• Do not add a second in-site Desktop history page here; if the fallback flow looks wrong, inspect the runtime fetch chain and the index deployment first

Star History

Track how the HagiCode-org/site repository has grown over time:

License

This repository is released under the terms in LICENSE.

---

Ready to explore the full product story? Visit hagicode.com and choose the experience that fits your workflow.