vibespecs

Org.Vibevm.Fractality.Fractality — Development skill for Claude Code

Development community

How to install Org.Vibevm.Fractality.Fractality

This entry records only its repository, not the path inside it, so there is no exact command to give. Open vibespecs/org.vibevm.fractality.fractality and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Org.Vibevm.Fractality.Fractality does

An agent operating system in its earliest form: fractality-mission-control (a scheduler daemon holding the agent roster, call tree, and usage metering) plus the fractality CLI, which lets an expensive boss agent delegate tasks to swarms of cheap worker agents running in isolated Claude Code processes under other model providers, exchanging everyth…

Alternatives in Development

LifeOS — ⛰️ The Life Operating System — an intent engineering platform that moves you from your current state to your i 18.7k ★
Octo Doctor — Environment diagnostics — check providers, auth, config, hooks, scheduler, and more 2.8k ★
Call Me — Minimal plugin that lets Claude Code call you on the phone 2.5k ★

README

fractality

An agent operating system in its earliest form.

One expensive, high-judgment agent (the **boss**) should not spend its context and its owner's budget on work a cheap model does well. fractality gives the boss a delegation fabric: task packets go in, isolated worker agents run them — Claude Code processes under *other* model providers (first: GLM 5.2 / GLM-5-Turbo via z.ai), in their own environments, worktrees, and config dirs — and everything comes back as **files on disk**: a result document, a branch, a transcript, a usage record.

At the center sits **`fractality-mission-control`** — a small Rust daemon that is the scheduler of this operating system: it spawns and supervises workers, holds the run registry and the call tree (agents spawning agents — hence the name), enforces budgets, kills whole process trees on demand, and meters everything. Its journal is the single telemetry store: scoreboards, delegation analytics, future GUIs and meta-cognition tooling all read from it. The long horizon — dedicated servers federating agents across machines — is deliberately designed-for but not built yet; think of the years when the Linux kernel and the GNU userland were young.

Design commitments (full text: [`vibevm/vibespecs/PROP-001-foundation.xml`](vibevm/vibespecs/PROP-001-foundation.xml)):

Process-level provider isolation, not proxying: a worker is a separate Claude Code process whose environment is constructed from scratch — it never inherits the boss's credentials. Enforced by tests.
Files are the only content channel between boss and workers.
Cross-platform Rust, one binary per role, no interpreter zoos.
Agent-neutral core: Claude Code is the first worker backend and the first boss harness, not a hard dependency of the model.
Clean-room with respect to every studied reference (`vibevm/vibespecs/refs/INVENTORY.xml`).
Fair use: one interactive boss session on a consume