Quickstart

Create and inspect a local child Session in one project.

1. Initialize the Worktree Root

cd /path/to/your/repo
asem init --interactive

The Init Wizard asks for a Workspace id, default Agent Template, and default Multiplexer Template. It writes .asem.yaml.

2. Check local commands

asem doctor

Doctor prints command availability for builtin Agent and Multiplexer Templates.

3. Create a child Session

asem session create reviewer-1 --profile reviewer --prompt "Review the current diff"

The child Session is launched through the selected Multiplexer Template. The prompt is written to that Session's launch files, and local Session metadata is stored in asem state.

If the selected Agent Template supports models, pass one explicitly:

asem session create reviewer-2 --profile reviewer --model sonnet --prompt "Review the current diff"

4. Inspect Sessions and Messages

asem session list
asem message list

Messages and Reports are scoped by Workspace and Worktree Root.

5. Open the Cockpit

asem tui

The Cockpit provides a keyboard-first view of local Sessions and details.

6. Register an AI client when needed

asem mcp add --for claude-code
asem skills add --for claude-code

MCP registration and Skill installation are separate. They update the selected Integration Target's local config and guidance files.

What just happened

• .asem.yaml defined project defaults.
• A child Session was created with explicit prompt shaping.
• Session and Message history stayed local to the Effective Scope.
• The TUI and MCP server can operate over the same local state.