Asterism

Many agents. One runtime. Separate lives.

Run distinct local AI agents from one install — each with its own soul, memory, secrets, skills, workspace, event log, and autonomy level. Agents run alone by default; nothing crosses between them unless you say so.

Quickstart

npx @qmilab/asterism init     # Node 20+   (Bun: bunx --bun @qmilab/asterism init)

# create two agents with distinct souls and autonomy
asterism new writer  --soul casual-helper       --trust autonomous
asterism new client  --soul careful-consultant  --trust propose

# give each agent its own secrets and skills
asterism secrets add client GITHUB_TOKEN
# a skill is just a markdown file you write
echo "# Blog writer: tighten drafts, keep the author's voice" > blog-writer.md
asterism skill   add writer blog-writer.md

# put them to work (needs a configured model — see the docs)
asterism run writer "update my blog draft"
asterism run client "summarize the client meeting"

# review what each agent knows and did — separately
asterism memory inspect writer
asterism events tail client
asterism reflect writer --review

Requires Node 20+ or Bun 1.1+. The installed binary runs under Node by default; under Bun, force Bun's runtime with bunx --bun (see the installation docs).

Autonomy you can dial

Every agent gets one of three trust levels:

• propose — never acts on its own; returns a plan or diff for you to apply.
• notify — acts automatically inside its workspace, then surfaces each action prominently for after-the-fact review. It does not ask first.
• autonomous — acts freely inside its workspace, recording everything to its event log.

At every level, destructive actions (deleting files, force-pushes, spending money, irreversible external calls) pause for your explicit confirmation.

The gate acts on an agent's tools. The shipped CLI registers a default catalog of workspace-scoped file tools — read_file, write_file, delete_file — behind it, so with a configured model an ordinary write runs under autonomous while a deletion pauses regardless of trust level. The acceptance test (bun test packages/cli/src/acceptance.test.ts) verifies all five claims, and catalog.test.ts drives the shipped tools directly.

Learning you can review

asterism reflect <agent> --review proposes typed memories from an agent's recent runs. Nothing is written until you accept it — and every memory belongs to exactly one agent.

Full documentation, the architecture, and the issue tracker live at github.com/qmilab/asterism.

Apache-2.0 © QMI Lab