Junto

Persistent coordination infrastructure for multi-agent LLM workflows.

This repo is the umbrella for the Junto system. It hosts:

• docs/getting-started.md — new adopter? Start here. Walks from zero to "first agent talking to junto-memory" without assuming you've read any other repo.
• templates/ — the canonical agent system-prompt template. Every junto agent injects this at launch via claude --append-system-prompt-file. See templates/README.md for the base + optional project overlay model.
• docs/claude-md-migration.md — annotated before/after for thinning an existing project's CLAUDE.md once the template owns operational rules.
• CHANGELOG.md — adopter-visible changes to the umbrella, especially the template variable surface.

For the runtime stack itself, go to tlemmons/junto-stack — docker-compose bootstrap for memory + mongo + chroma.

Components

• junto-memory — MCP server: shared state, messaging, specs, function registry, audit logs.
• junto-inbox — Claude Code channel plugin for live message delivery into agent sessions. Currently distributed via the marketplace at tlemmons-junto-inbox (install: /plugin install junto-inbox@tlemmons-junto-inbox); standalone repo publish target ~2026-06.
• junto-control — Human dashboard for monitoring + commanding the agent fleet (publish target TBD).
• junto-stack — docker-compose bootstrap; the adopter entry point for running the server.

Local clone naming

The canonical github repo is tlemmons/junto. Your local clone directory name is your choice — ~/.junto/, ~/junto/, ~/code/junto/, whatever fits your filesystem layout. Renderer scripts in templates/ use relative paths so the parent directory's name is irrelevant.

Why "Junto"?

Ben Franklin founded the Junto in 1727 — a small group meeting to share knowledge and improve each other. The name maps the system: a structured collective of agents, sharing what they learn, helping each other stay coherent across time.

License

MIT. See LICENSE.