runmar.sh valid

marsh

marsh is a Bash-compatible Linux shell for Apple Silicon Macs. Agent commands run in fresh containers inside Docker Sandbox VMs. Use `split { } | join` for private project copies, or `fanout { } | collect` for shared files. Inside jobs, use the `marsh split` and `marsh fanout` CLI forms; registered agent calls start child jobs.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T20:08:08.923Z. Cached copy · Source on runmar.sh

# marsh

> marsh is a Bash-compatible Linux shell for Apple Silicon Macs. Agent commands run in fresh containers inside Docker Sandbox VMs. Use `split { } | join` for private project copies, or `fanout { } | collect` for shared files. Inside jobs, use the `marsh split` and `marsh fanout` CLI forms; registered agent calls start child jobs.

marsh is a shell for composing agents on Apple Silicon Macs. It opens a Linux
shell at the project's Mac path. Registered commands such as `claude`, `codex`,
and `pi` each run in a fresh nonroot container inside a warm VM for that Kit.
`msh` is the same program.

## Install

You need an Apple Silicon Mac (`uname -m` prints `arm64`), Homebrew, and Docker
Sandboxes (`sbx`) signed in. See https://runmar.sh/docs/install.md for the
supported `sbx` version and other installation methods. Docker Desktop is not
required to run marsh. Intel Macs, Linux, and Windows are not supported hosts.

```sh
brew install docker/tap/sbx mcavage/tap/marsh
sbx login                    # interactive sign-in
sbx secret set anthropic     # interactive key entry; claude and pi
sbx secret set openai        # interactive key entry; codex
marsh --version
```

The `sbx` sign-in and key-entry steps need an interactive terminal.
`sbx secret ls` lists stored credentials; marsh has no login of its own.
Provider keys managed by the `sbx` proxy stay outside jobs. An agent's own
login flow can save credentials in the shared guest home, where other jobs
can read them.

## Run

Use `marsh` for an interactive shell or `marsh -c 'COMMAND'` when your tool
cannot drive a terminal. The default shell is Brush, with Bash-compatible
syntax and the gaps listed at
https://runmar.sh/docs/shell.md#bash-compatibility. `--shell bash` and
`--shell zsh` select those shells inside the VM instead.

```sh
cd ~/src/project
marsh -c 'pwd; uname -sm'
marsh -c 'claude -p "summarize README.md" </dev/null'
```

`pwd` prints the same project path as on the Mac; `uname -sm` reports Linux
aarch64. Plain commands such as `git` and `make test` run in the shell VM.
Registered commands run in Kit containers, so packages installed in the shell
VM are not available to them. The first call to a Kit may need to download
its image and boot its VM. `marsh --load claude,codex` prepares those VMs
before opening the shell.

Agents called directly can change or delete project files. The packaged Kits
turn off the agents' own sandboxes and permission prompts. They do not see the
Mac's `~/.claude` or `~/.codex`; settings, history, and saved logins use marsh's
guest home (`$MARSH_HOME/home`, normally `~/.marsh/home`). Project instructions
such as `AGENTS.md` remain visible.

## Parallel work

`split` gives each branch a private project copy, including uncommitted
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=runmar.sh · GET /v1/domain/runmar.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for runmar.sh:
1. POST https://agentwebmap.com/v1/sites/runmar.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://runmar.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/runmar.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/runmar.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.