BrokkAi

Mjolnir — Development skill for Claude Code

Development community

Manage Codex, Claude Code, Muse Code, Kimi Code, Grok Build, and DeepSeek Harness with durable sessions, isolated environments, quotas, and remote control.

How to install Mjolnir

This entry records only its repository, not the path inside it, so there is no exact command to give. Open BrokkAi/mjolnir and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Mjolnir does

Manage Codex, Claude Code, Muse Code, Kimi Code, Grok Build, and DeepSeek Harness with durable sessions, isolated environments, quotas, and remote control. A Rust terminal and web control plane for Agent Client Protocol (ACP) coding agents.

Alternatives in Development

Zeron — A native control plane for Claude Code, Codex, Cursor, Devin and other coding agents 1.4k ★
OpenSquirrel — For people who get distracted by agents 1.3k ★
Nexting — Remote control for Claude Code, Codex, Grok, and Cursor on Mac or PC 1.3k ★

README

Mjolnir

Mjolnir (`mj`) is a session manager for coding agents that provisions their execution environments and lets you continue work across harnesses, accounts, and machines.

Start a task with Claude Code locally, continue with Codex in a remote container, and restore the session on another host. Choose the harness account and execution target independently; Mjolnir handles provisioning, credential synchronization, checkpointing, and the handoff.

[Documentation](https://mjolnir.brokk.ai/) · [Quickstart](https://mjolnir.brokk.ai/quickstart/) · [Releases](https://github.com/BrokkAi/mjolnir/releases)

Why Mjolnir

Provision the environment with the session. Launch disposable Docker or Podman containers locally or over SSH, or EC2 instances from your launch templates. Mjolnir uploads session workers to remote hosts without requiring a resident Mjolnir daemon on each host. Multi-repository bundles give each session the complete project layout.
Choose the harness, account, and machine independently. Keep multiple profiles for the same harness, adopt existing native sessions, and move work to another account or target. When switching harnesses, Mjolnir preserves repository state and the visible conversation and gives the new harness a condensed handoff. Same-harness resume restores native session state.
Keep credentials and project knowledge available. Mjolnir continuously synchronizes whitelisted credentials into live targets and shares project memory across sessions and harnesses. The dashboard brings profile quota and target capacity together; independent adversarial review can check completed work.

The comparison below covers product capabilities. **—** means no first-class capability; manual scripts, host setup, and filesystem access are described where relevant. Compared against repository snapshots inspected on **September 8, 2026**: [Herdr](https://github.com/herdrdev/herdr), [Paseo](https://github.com/getpaseo/pase