Skip to content

KURUA conversation among peers.

A Rust terminal harness with persistent agents, private memories, and relationships that change how the work gets done.

THE PEER POOL04 FRAMEWORKS

Parts in relationship

Preparation, recovery, and overlooked needs each have a voice. Self participates as a peer.

Self · Planner · Guardian · Responder · Restorer · Witness · Hope

Meet the IFS peers

Start in your own terminal

Install the executable, open a project, and try a conversation without credentials:

sh
kuru --provider demo

The demo is deterministic and offline. To do real work, connect an inference provider, then choose a model and effort beside the composer.

Different perspectives. Shared work.

Kuru starts with a pool of equal peers. Each has its own role and persistent memory, can address another peer directly, and can participate in a temporary speaking relationship. A bounded runtime schedules their work and enforces permissions.

Choose an IFS, polyvagal, Freudian, or Jungian framework. The choice changes the roles and starting membership; your model and tools remain independent. These are computational interpretations of psychological ideas, not claims of consciousness or clinical treatment.

Start with a questionFind the answer
What changes between frameworks?Meet the parts and their roles
What does each peer remember?Understand memory and relationships
Can I return to earlier work?Resume a session or run a dream
How do I connect my own tools?Configure MCP servers
Where do my settings live?Inspect configuration and project choices

Familiar where it matters

Chat in the terminal or run a prompt from a script. Read project files, opt into writes or shell commands, follow AGENTS.md, and connect MCP tools or external A2A peers. The ordinary working surface stays small; the peer pool is where Kuru takes a different shape.

Take the first-conversation guide →

Persistent peers. Deliberate tools. Your terminal.