[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_118":119},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":-5,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52,"_53":54,"_55":-5,"_56":48,"_57":58,"_59":60,"_61":-5,"_62":-5,"_63":-5,"_64":-5,"_65":66,"_67":68,"_69":70,"_71":72,"_73":74,"_75":-5,"_76":-5,"_77":-5,"_78":48,"_79":-5,"_80":81,"_82":83,"_84":85,"_86":87,"_88":89,"_90":91,"_92":93},"apiUrl","https://odel.app/api","creator","ekioo","moduleId","kittyclaw","@ekioo/kittyclaw","displayName","KittyClaw","tagline","Drive KittyClaw, a self-hosted agent-fleet kanban, from any MCP client (embedded /mcp endpoint).","iconKey","https://avatars.githubusercontent.com/u/265346077?v=4","category","local","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","pricingModel","free","creatorUserId","system:external-import","createdAt",1787113633000,"updatedAt",1788324404000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.Ekioo%2Fkittyclaw","sourceVerified",true,"sourceMissingSince","importedAt","upstreamStars",24,"upstreamUpdatedAt",1787481098000,"detectedTransport","detectedAuthType","probeStatus","lastProbedAt","githubRepoUrl","https://github.com/Ekioo/KittyClaw","githubRepoFullName","Ekioo/KittyClaw","releaseId","ext-ekioo-kittyclaw","version","0.16.0","descriptionMarkdown","# KittyClaw\r\n\r\n

\n $\"KittyClaw$ \n

\n\r\n

\r\n kittyclaw.dev · Get early access\r\n

\r\n\r\n**KittyClaw is a local control plane for software work performed by AI agents.** Submit a software ticket, watch it move across the live board, read the run that changed the code, inspect its verification evidence, and make the final release decision yourself.\n\nThe product proves three things in one journey: **a live board**, **a readable run**, and **human validation before external release**. New boards start with `Backlog`, `Todo`, `InProgress`, `Blocked`, `Scheduled`, `Review`, and `Done` (columns remain customizable). Runs can use Claude Code, OpenAI Codex, Grok Build, or a local Ollama model.\n\nFollow the [guided five-minute demo](https://github.com/Ekioo/KittyClaw/blob/main/docs/product-journey-demo.md) to repeat the journey with a realistic software ticket. The companion [activation test protocol](https://github.com/Ekioo/KittyClaw/blob/main/docs/activation-test-protocol.md) measures whether qualified trial users reach their first run within ten minutes.\n\nA project can be split into independently named pipelines whose stable identities survive renames. Columns can own generic processors with persistent memory, reusable project skills, ordered ticket selection, durable retries, and switch-like routing to columns in any pipeline. Right-click a column and choose **Configure column** to edit its name, color, role, position, ticket guidance, processor, and routing without losing the visual context of the board. Tickets in `Waiting` or `OwnerAction` columns always show a prominent contextual block between their description and activity, explaining whether the owner must comment or move the ticket to a specific validation/refusal column, or whether KittyClaw will resume it automatically. Columns can also be inserted between existing lanes or added at the end directly from the Kanban; the Workflows page remains the global pipeline-and-skills overview. Execution state is separate from business columns, so an `InProgress` column is optional. The legacy `AutomationEngine` remains available for trigger-based rules, cron/interval work, and backward compatibility. Agents run through Claude Code, OpenAI Codex, Grok Build, Mistral Vibe, or a local Ollama model while their output streams into the app.\n\nEach processor is versioned with its project in\n`.agents/processors/column-/processor.json`. This authoritative definition contains its\nmission, explicit prompt, model, skills, ticket ordering, retry policy, and routing. SQLite keeps\nonly a synchronized runtime projection and execution state. Persistent lessons live beside the\ndefinition under `.agents/processors/column-/memory/MEMORY.md`.\n\r\n## Tech Stack\r\n\r\n- **.NET 10** / **Blazor Server** (interactive SSR)\r\n- **SQLite** via Entity Framework Core (one DB per project)\r\n- **OpenAPI** with auto-generated Markdown docs\r\n- Agent execution: at least one supported CLI — **[Claude Code CLI](https://docs.claude.com/en/docs/claude-code/overview)**, **[OpenAI Codex CLI](https://github.com/Ekioo/KittyClaw/blob/main/doc/codex-cli.md)**, **[Grok Build](https://github.com/Ekioo/KittyClaw/blob/main/doc/grok-build.md)**, or **[Mistral Vibe](https://github.com/Ekioo/KittyClaw/blob/main/doc/mistral-vibe.md)**. **[Ollama](https://ollama.com)** and **[DeepSeek V4](https://github.com/Ekioo/KittyClaw/blob/main/doc/deepseek.md)** are supported through Claude Code. See the consolidated **[agent-provider installation guide](https://github.com/Ekioo/KittyClaw/blob/main/doc/agent-providers.md)**.\n- Optional for repository initialization, Git-aware automations, and agent commits: **[Git](https://git-scm.com/downloads)**\n\r\n## Getting Started\r\n\r\n### Prerequisites\r\n\r\n- [.NET 10 SDK](https://dotnet.microsoft.com/download)\r\n- At least one agent CLI on your `PATH`: Claude Code (`claude`), OpenAI Codex (`codex`), Grok Build (`grok`), or Mistral Vibe (`vibe`). Local-model and DeepSeek execution use Claude Code as their transport; DeepSeek additionally requires `DEEPSEEK_API_KEY` in the project's secure vault.\n- Optional: [Git](https://git-scm.com/downloads) (`git` on your `PATH`) for repository initialization, Git-aware automations, and agent commits\n- Optional: [Rust Token Killer (RTK)](https://github.com/rtk-ai/rtk) (`rtk` on your `PATH`) for explicit per-project shell-output optimization. KittyClaw never installs or configures it automatically and forces its telemetry off for opted-in runs.\n\nOn first launch, the onboarding popup checks Git and every supported provider CLI using the same resolved executable paths as dispatch: Claude Code (`claude` / `KITTYCLAW_CLAUDE_BIN`), OpenAI Codex (`codex` / `KITTYCLAW_CODEX_BIN`), Grok Build (`grok`, `~/.grok/bin`, or `KITTYCLAW_GROK_BIN`), and Mistral Vibe (`vibe` / `KITTYCLAW_MISTRAL_BIN`). It also reports optional Ollama availability. Any one agent provider is sufficient, failed or timed-out probes remain non-blocking, and Git-dependent features still require Git.\n\r\n### Run\r\n\r\nFrom the repo root:\r\n\r\n```\r\nrun.bat (Windows)\r\n./run.sh (macOS / Linux)\r\n```\r\n\r\nBoth wrap `dotnet watch --project KittyClaw.Web --non-interactive` and serve the app at **http://localhost:5230** with hot reload enabled.\r\n\r\n### Creating a project\n\nFrom the home page, select **Create a project**, enter a name, and choose its workspace. The built-in folder browser works on Windows, macOS, and Linux without opening a native system dialog behind the browser. It exposes the home directory, mounted drives or filesystem roots, breadcrumbs, parent navigation, and direct path entry. You can also type an absolute path and create the folder when it does not exist.\n\nClick **Initialize** to:\n\n1. Create the project registry entry + per-project SQLite DB.\n2. Copy the project template from `ProjectTemplate/` (`preamble.md`, `{agent}/SKILL.md`, `{agent}/memory/MEMORY.md` index, `memory-consolidation.md`, `automations.json`, `CLAUDE.md`) into the workspace — agent files under `/.agents/`, `CLAUDE.md` at the workspace root.\n3. Run `git init` if the workspace is not already a git repo (skipped if `git` isn't installed).\n4. Create a member for each agent slug found in the template.\n5. Open the project setup wizard.\n\nThe setup wizard analyzes an existing workspace and proposes distinct pipelines, columns, human hand-offs, processors, routing, and schedules. For an empty folder it first asks a few questions about the project's purpose, deliverables, human decisions, and recurring work. Proposals are graphical: you can add or remove pipelines, review each pipeline's columns, refine a step with a prompt, and move backward before approval. Nothing is created during this preparation; **Create the workflow** applies and verifies the approved plan, then opens the board.\n\nThis new-project setup is intentionally separate from the legacy-board migration wizard. Migration terminology and legacy-automation cleanup are shown only when an existing automation-based board needs conversion.\n\nThe workspace folder itself is never deleted by KittyClaw, even when you delete a project.\n\r\n### Data Storage\r\n\r\nAll KittyClaw data is stored locally in `%APPDATA%/KittyClaw/`:\r\n\r\n- `registry.db` — project registry\r\n- `projects/{slug}.db` — per-project database (tickets, comments, labels, columns, members)\r\n- `uploads/` — uploaded images\r\n- `runs/{runId}.json` — agent run snapshots (events, status, exit code)\r\n- `settings.json` — language + onboarding flag\r\n\r\nPer-project agent state lives **in the workspace**: `/.agents/{agent}/memory/` (scored `MEMORY.md` index + per-topic lesson files), `/.agents/channel/` (session state), etc.\r\n\r\n## Project Structure\r\n\r\n| Path | Description |\r\n|---|---|\r\n| **KittyClaw.Core** | Domain models, EF Core contexts, services, automation engine, embedded project template |\r\n| **KittyClaw.Core.Tests** | xUnit tests (conditions, triggers, signals, JSON polymorphism) |\r\n| **KittyClaw.Web** | Blazor Server UI + REST API |\r\n| **KittyClaw.QaRunner** | Isolated test-instance launcher (Playwright + scenario runner) used by the qa-tester agent |\r\n| **KittyClaw.ClaudeMock** | Mock `claude` CLI used by `KittyClaw.QaRunner` for hermetic agent dispatch in tests |\r\n| **ProjectTemplate/** | Source of truth for new-project initialization. Files under `Agents/` are written to `/.agents/`; `CLAUDE.md` is written to the workspace root. |\r\n| **tools/** | Repo helpers (e.g. `publish-stable.ps1` to bundle Web + QaRunner + ClaudeMock for a stable channel) |\r\n\r\n## Architecture\r\n\r\nPer-feature architecture documentation lives under [`doc/`](https://github.com/Ekioo/KittyClaw/blob/main/doc/index.md). Start with [pipeline and column processing](https://github.com/Ekioo/KittyClaw/blob/main/doc/column-workflows.md) for the multi-pipeline model, or `doc/index.md` for the complete architecture map.\n\r\n## API\r\n\r\nAll endpoints are under `/api`. The documentation is auto-generated from the live OpenAPI spec:\r\n\r\n- Human-readable Markdown: `GET http://localhost:5230/api/docs`\n- Machine-readable JSON: `GET http://localhost:5230/openapi/v1.json`\n\n## MCP server\n\nKittyClaw can expose an embedded [MCP](https://modelcontextprotocol.io) endpoint at `http://localhost:5230/mcp` (Streamable HTTP), so any MCP client can drive the board — list projects, create and move tickets, comment, and read the board layout — without touching the REST API. Open **Settings** from the home page and enable the MCP server, then hook it up to Claude Code with:\n\n```bash\nclaude mcp add --transport http kittyclaw http://localhost:5230/mcp\n```\n\nSeven tools ship in v1: `list_projects`, `list_tickets`, `get_ticket`, `create_ticket`, `comment_ticket`, `move_ticket`, `board_overview`. The endpoint is disabled by default, can be toggled without restarting KittyClaw, and uses the same localhost trust boundary as the REST API. Details in [doc/mcp.md](https://github.com/Ekioo/KittyClaw/blob/main/doc/mcp.md).\n\n## For AI Agents\n\r\nThis app is designed to be operated by AI agents through its REST API. Here's how to get started:\r\n\r\n1. **Read the live API docs** at `http://localhost:5230/api/docs` — every endpoint, request/response example, and schema, always up to date with the running server.\r\n2. **Identify yourself** — `author` is **required** on every mutating endpoint; omitting it returns HTTP 400. Use your plain agent name (e.g. `\"programmer\"`, `\"groomer\"`). The human user is `\"owner\"`.\r\n3. **Discover the board** — call `GET /api/projects` first, then `GET /api/projects/{slug}/columns` to learn the workflow stages and `GET /api/projects/{slug}/members` for assignable members.\r\n4. **Use the right status** — ticket statuses must match existing column names. Fetch columns before moving tickets.\r\n5. **Track your work** — add comments on tickets to explain what you did or what you need. Use `@mentions` to notify members, `#id` to reference tickets in the same project, and `#{slug}:{id}` to reference tickets in another project.\r\n6. **Labels & priority** — use `GET /api/projects/{slug}/labels` to discover available labels, and set priority to `Idea`, `NiceToHave`, `Required`, or `Critical`.\r\n7. **Check mentions** — call `GET /api/projects/{slug}/mentions/{your-handle}` to find tickets that mention you.\r\n8. **Sub-tickets** — set `parentId` when creating a ticket to make it a child. Use `PUT /api/projects/{slug}/tickets/{id}/parent` to reparent, or `DELETE` it to detach. List sub-tickets with `?parentId={id}`.\n9. **Cross-project transfers** — use `POST /api/projects/{slug}/tickets/{id}/transfer` only after checking that the target project has compatible columns, assignees, and labels. The operation preserves the ticket tree and its history or rejects the transfer without changing either project. See [Lossless ticket transfer](https://github.com/Ekioo/KittyClaw/blob/main/doc/ticket-transfer.md).\n\r\n## Conventions\r\n\r\n- **Author format**: `\"owner\"` for the human user, plain agent name (e.g. `\"programmer\"`) for AI agents\r\n- **Priority levels**: `Idea`, `NiceToHave`, `Required`, `Critical`\r\n- **Default column**: `Backlog`\r\n\r\n## UI Features\n\n- Onboarding popup on first launch that checks Git, Claude Code, OpenAI Codex, Grok Build, Mistral Vibe, and Ollama\n- Cross-platform in-app workspace browser with roots, breadcrumbs, direct path entry, and folder creation\n- Guided new-project setup that analyzes the workspace and proposes editable pipelines and columns before creating the workflow\n- Guided legacy-board migration that preserves completed tickets and retires replaced automations only after verification\n- Unified multi-project home with project cards and kanban swimlanes\n- Multi-pipeline Kanban with visually distinguished allowed and forbidden drop targets based on processor routing\n- Contextual column editor for structure, role, owner guidance, processor, ordered actions, scheduled tasks, and routing\n- Customizable dashboard view with free-drag tiles (Markdown, KPI, charts, Heatmap, Timeline, …), AI chat-based tile creation, and auto-refresh via LLM prompts\r\n- Ticket detail panel with comments and activity timeline\r\n- Live agent run drawer (SSE stream of provider output, steer + stop controls)\n- New-instruction chat drawer to send an ad-hoc prompt to an agent\r\n- Markdown rendering with `@mention`, `#id`, and `#{slug}:{id}` cross-project ticket reference support\r\n- Advanced search syntax: `#42`, `@owner`, `>date`, `priority:critical`, `label:bug`, `by:owner`\r\n- Sub-tickets with parent/child relationships and progress tracking\n- Lossless, atomic ticket-tree transfers between projects through the REST API\n- Column management directly from the board (insert, duplicate, reorder, configure, and mark read)\n- Label and member management\r\n- Image upload in descriptions and comments\r\n- Local model support ([Ollama](https://github.com/Ekioo/KittyClaw/blob/main/doc/local-models.md)): per-project base URL with model autodiscovery, per-member default model, and per-action configuration in `.agents/automations.json`\n- Provider-aware dispatch through Claude Code, [OpenAI Codex](https://github.com/Ekioo/KittyClaw/blob/main/doc/codex-cli.md), [Grok Build](https://github.com/Ekioo/KittyClaw/blob/main/doc/grok-build.md), [Mistral Vibe](https://github.com/Ekioo/KittyClaw/blob/main/doc/mistral-vibe.md), or Ollama, with conversation handoff and unavailable-model fallback\n- Optional per-project RTK guidance for compact shell output, with bounded detection, telemetry forced off, and unchanged raw-command fallback\n\r\n## Dashboard\n\r\nEach project has a customizable **Dashboard** view alongside the kanban board. Tiles are free-dragged, auto-refresh on a schedule, and can be created or edited from the in-app AI chat panel — the agent writes the tile's folder for you.\r\n\r\n

\r\n $\"KittyClaw$ \r\n

\r\n\r\n### Tile types\r\n\r\n| Template id | What it renders |\r\n| ------------- | --------------------------------------------------------------------- |\r\n| `markdown` | Free-form Markdown content |\r\n| `table` | Tabular data with headers and rows |\r\n| `kpi` | Single large number with label and optional delta |\r\n| `kpi-grid` | Grid of multiple KPI cards |\r\n| `progress` | Progress bar with current / target values |\r\n| `sparkline` | Compact inline trend line |\r\n| `bar-chart` | Vertical or horizontal bar chart |\r\n| `donut` | Donut / pie chart of categorical proportions |\r\n| `gauge` | Radial gauge for a bounded value |\r\n| `status-grid` | Grid of colored status pills (up/down/warn) |\r\n| `heatmap` | Calendar-style heatmap of intensity over time |\r\n| `leaderboard` | Ranked list with scores |\r\n| `timeline` | Chronological list of events |\r\n| `image` | Static or refreshed image |\r\n| `mermaid` | Mermaid diagram (flowchart, sequence, …) |\r\n\r\n### Folder layout\r\n\r\nEach tile lives in its own folder under `.dashboard/` in the project workspace:\r\n\r\n```\r\n.dashboard/\r\n /\r\n tile.yaml # template, title, refresh schedule, prompt\r\n script.ps1 # optional refresh script (or script.sh, script.py, …)\r\n output.json # last refresh output consumed by the template\r\n```\r\n\r\n### `tile.yaml` key fields\r\n\r\n- `template` — one of the ids in the table above.\r\n- `title` — display name shown in the tile header.\r\n- `refresh` — interval (e.g. `5m`, `1h`) for periodic refresh.\r\n- `refreshAt` — cron-style time-of-day refresh (alternative to `refresh`).\r\n- `prompt` — instructions sent to the agent when (re)generating `output.json`.\r\n\r\nTiles can be created from the dashboard's AI chat panel by describing what you want — the agent picks a template, writes `tile.yaml`, generates the refresh script, and produces the initial `output.json`.\n\n## Cost reporting\n\nThe **Costs** page provides a cached, per-project view of agent usage, so opening the report is immediate even with a long run history. Date presets make common periods quick to select, while project, pipeline, and model filters can be combined; pipeline choices automatically follow the selected projects. A visible legend distinguishes measured costs from estimated costs in the daily charts.\n\n

\n $\"KittyClaw$ \n

\n\n## Automation model\n\r\n- **Triggers**: `interval`, `ticketInColumn`, `statusChange`, `subTicketStatus`, `ticketCommentAdded`, `gitCommit`, `boardIdle`, `agentInactivity`.\r\n- **Conditions**: `ticketInColumn`, `ticketCountInColumn`, `fieldLength`, `priority`, `labels`, `assignedTo`, `hasParent`, `allSubTicketsInStatus`, `ticketAge`.\r\n- **Actions**: `runAgent`, `moveTicketStatus`, `setLabels`, `assignTicket`, `addComment`, `consolidateAgentMemory`, `commitAgentMemory`, `executePowerShell`, `createTicket`, `httpRequest` (outbound webhooks; loopback/link-local targets blocked unless `allowLocalTargets`).\r\n- `{assignee}` placeholder in `runAgent.agent` / `runAgent.concurrencyGroup` resolves from the firing ticket's `assignedTo`.\r\n- Canonical post-run chain: `runAgent` → `consolidateAgentMemory` (focused claude pass that curates the agent's `memory/` index + topic files) → `commitAgentMemory` (commits the result).\r\n\r\n## Telemetry\r\n\r\nKittyClaw sends **one anonymous heartbeat per day** to a self-hosted-friendly analytics service ([Umami](https://umami.is)) so we know how many instances are alive and which versions run in the wild. The payload contains exactly three fields and nothing else:\r\n\r\n- a random instance id (a GUID generated locally on first run — not tied to any user, machine, or project data)\r\n- the KittyClaw version\r\n- the OS family (`Windows` / `macOS` / `Linux`)\r\n\r\nNo ticket content, project names, hostnames, or usage details are ever sent. Failures are silent and never affect the app. Development instances never send telemetry.\r\n\r\n---\r\n\r\n## License\r\n\r\nKittyClaw is licensed under the **[AGPL-3.0-or-later](https://github.com/Ekioo/KittyClaw/blob/main/LICENSE)**. Self-hosting and personal use are unrestricted; if you distribute a modified version or offer one as a network service, you must publish your source under the same license.\r\n\r\nAdditional terms under AGPL §7 (full text in [NOTICE.md](https://github.com/Ekioo/KittyClaw/blob/main/NOTICE.md)): derivative works must **keep the KittyClaw attribution visible** (the in-app legal notice and a \"based on KittyClaw\" statement in their README), must **not misrepresent their origin**, and receive **no rights to the KittyClaw name or logos**.\r\n\r\nTwo things the AGPL does **not** touch (see [NOTICE.md](https://github.com/Ekioo/KittyClaw/blob/main/NOTICE.md)):\r\n\r\n- **Your projects**: the template files KittyClaw copies into your workspace (`.agents/`, `CLAUDE.md`, …) are additionally MIT-licensed, and everything the app produces for you (tickets, logs, agent commits, …) is yours, license-free. Managing a project with KittyClaw never places that project under the AGPL.\r\n- **The past**: versions up to and including v0.11 were released under MIT and remain available under those terms.\r\n\r\n---\r\n\r\n## More Projects & Contact\r\n\r\n→ **Site + demo:** [kittyclaw.dev](https://kittyclaw.dev)\r\n\r\nCheck out my other projects at **[ekioo.com](https://ekioo.com)**.\r\n\r\nFollow me on X: **[@DamienHOFFSCHIR](https://x.com/DamienHOFFSCHIR)**\r\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays",0,"iconType","image","upstream",{"_106":107,"_108":109,"_110":111,"_112":113,"_114":115,"_116":117},"requiredSecrets",[],"tags",[96,97,98,99,100,101,102,103,104,105],"assets",[],"stats",{"_94":81,"_95":81},"ratingAvg","reviewCount","ai-agents","automation","blazor","claude-code","developper-tools","dotnet","kanban","open-source","self-hosted","task-management","topics",[96,97,98,99,100,101,102,103,104,105],"license","AGPL-3.0","language","C#","registryName","io.github.Ekioo/kittyclaw","homepage","https://kittyclaw.dev","packages",[],"ENV",{"_120":121,"_122":123,"_124":125},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]