// the forge · CR v1.5.1 · open source · MIT

Forge a fleet
from one claude
subscription.

Open-source mission control for Claude Code. Run parallel agents across every project, spin up a hivemind, and schedule work that fires overnight — then check in from your phone like a group chat with your fleet.

Local-first · no cloud markup Bring your own Claude MIT · forever free Phone-tunneled
Clayrune dashboard with project tiles, status indicators, and agent activity feed
// fleet · live
7agents
↑ 1.4M tokens · $2.41 · 0 incidents
hover to focus
// the idea

Pick any project back up right where you left off. Collaborate via GitSync, explore with Hivemind, answer your AI from your phone — and keep it all local. Nothing leaves your machine but what you send your provider.

§ 01
// anywhere.md

From every pocket.
To every project.

An attested Cloudflared tunnel plus a mobile UI that feels like a messaging app — chat list of projects, drill-down threads, unread badges, paste-screenshots-into-prompts. Your fleet is one notification away.

SECTION 01.ATUNNEL · MOBILE UI · LIVE-SYNC
// chat list
Clayrune mobile home — chat list of projects with live status, schedule banner, and bottom nav
§ 02
// features · nine surfaces

Nine surfaces. One binary.

SECTION 02.AFLEET · MEMORY · HIVEMIND · SCHEDULE · SKILLS · MCP · MOBILE · MULTI-WIN · SYNC

Tile fleet

Every project a tile. Every tile its own agents, streaming live.

Per-project memory

A MEMORY.md per project. Conventions and context persist across sessions.

Hivemind

One orchestrator decomposes a goal and spawns workers across repos.

Scheduler

Cron and interval routines that fire work while you sleep.

Skills

Authored or auto-distilled. Promote one to global in a click.

MCP servers

Wire tools per project — scoped, never leaking across boundaries.

Mobile tunnel

Attested Cloudflared tunnel. Run your fleet from a chat-list on your phone.

Multi-window

Watch many agents at once, each in its own streaming pane.

GitHub sync

Backlog ↔ Issues, bidirectional. GitSync keeps peers in step.

§ 03
// boundaries

Isolated by default.
Connected when you say so.

Every project is its own sandbox — memory, backlog, skills, MCP, accent color, conventions. Nothing leaks across by accident. When you do want them to talk — a cross-repo hivemind, a shared skill, a shared rule book — the seams are explicit.

SECTION 03.A04 BOUNDARIES · 03 BRIDGES
▸ Default: full isolation

One project's MEMORY.md, skills, and MCP servers never leak into another's context.

▸ Promote a skill to global

Authored a skill that should help everywhere? Promote it once — it appears in every project's pack.

▸ Cross-project hivemind

One goal, workers spawned across repos. Coordinated by the orchestrator, observable from the same chat list.

▸ Shared rules & shared memory

SHARED_RULES.md + the engram memory layer give the fleet a common language without dropping per-project boundaries.

// get clayrune

Up and running in under a minute.

Prebuilt binary for Windows, or run from source on macOS · Linux · WSL. Everything you need is on the download page.

§ 06 · BUILT IN THE OPEN

The whole Clayrune frontend is one HTML file.
Come carve a rune.

MIT-licensed. No framework lock-in, no build pipeline. Bug? Open an issue. Idea? Open a PR. Want a new connector — Linear, Notion, Slack? The Flask backend is small and friendly. The platform binding (mc_remote + mc_tunnel) is a thin shell over an MIT seam — implement the contract and plug in your own.

Forged in production by an operator who needed it. It's better when more hands shape it.

184commits
v1.5.1latest release
html file
MITlicense