mcpField
A
alera-cli

alera-cli

github.com/leynierAgent workflows4143 installsUpdated 3d ago
Repository

About alera-cli

alera-cli is a workflow guide for operating Alera resources through its managed CLI, aimed at coding agents handling workspaces, hosts, and runtime tasks. It emphasizes loading only the relevant workflow and preserving boundaries around managed worktrees and runtime metadata.

Key features

  1. 01Manage workspaces and worktrees
  2. 02Configure SSH hosts and remote workspaces
  3. 03Inspect inboxes and agent profiles
  4. 04Check and install agent skills
  5. 05Get structured output with JSON

Use cases

  1. 01Add or remove a managed workspace
  2. 02Set up an SSH remote workspace
  3. 03Ask a running agent a question externally
  4. 04Check skills installed on the machine

MCP support

The guide covers signing the Alera runtime into an account and allowing MCP clients to drive it through MCP Control or `alera mcp serve`.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/leynier/alera --skill alera-cli

After installing, type/alera-cliin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
automations.md
hosts.md
inbox.md
mcp.md
recovery.md
workspaces.md

Details

From the project README

Alera CLI

Use the managed alera CLI for Alera resources. Inside Alera terminals, its shim and ALERA_RUNTIME_DIR select the UI's runtime profile. Use command-group --help for flags and --json for structured output; list envelopes use items.

Choose The Relevant Workflow

  • Projects, worktrees, hand-off/hand-on, linked issues, Watch and Fix, tags, tabs, relations, and sections: read workspaces.
  • SSH targets and remote workspace setup: read hosts.
  • Scheduled agent work: use the alera-automations skill; CLI entry points are in automations.
  • Missing runtime host, external-shell configuration, metadata repair, or a tab that stopped showing its agent's status: read recovery.
  • Agent Profile inspection, launch, or maintenance: use the alera-agent-profiles skill. Its simple-maintenance route does not require catalog research.
  • Asking a running agent a question from outside its terminal, or reading an inbox: read inbox.
  • Agent dispatch, worker tasks, or coordinator lifecycle: use the alera-orchestration skill.
  • Signing the runtime in to an Alera account, naming it, or letting MCP clients drive it (MCP Control, alera mcp serve): read mcp.
  • Checking or updating the Alera skills installed for coding agents on this machine: alera skill status compares each one with this runtime, and alera skill install [--skill <name>] installs them at this runtime's own commit.

Load only the workflow needed for the current request.

Workspace Invariants

Use workspace add/remove for real managed worktrees. Use register/unregister only for intentional metadata repair; register --host-id does not create a remote worktree. SSH bootstrap installs only the sidecar; workspace add --host-id creates the remote worktree.

Do not use raw git worktree add/remove or edit runtime metadata unless the user requests low-level recovery. Inspect exact IDs and state before destructive operations. Keep user-created branches unless deletion is explicitly requested; default removal deletes only branches Alera created. Use workspace rename to change a workspace's display name; it never renames the branch or worktree folder. Use workspace focus to select and show an existing workspace in the running desktop app; it fails instead of starting Alera. Use workspace pin/unpin for sidebar placement. Use workspace section to assign sidebar sections; do not edit runtime.sqlite to assign sections.

Comments

Markdown supported