Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
docker run -i --rm ghcr.io/runewardd/runeward:v0.1.4O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
RUNEWARD_CONFIG_DIR=<value> RUNEWARD_STATE_DIR=<value> claude mcp add io.github.runewardd-runeward -- docker run -i --rm ghcr.io/runewardd/runeward:v0.1.4Execute em um terminal.
{ "mcpServers": { "io.github.runewardd-runeward": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/runewardd/runeward:v0.1.4" ], "env": { "RUNEWARD_CONFIG_DIR": "<value>", "RUNEWARD_STATE_DIR": "<value>" } } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Put enforceable policy, human approvals, isolated execution, budgets, and signed evidence around any AI agent. Runeward works with an existing agent or multi-agent framework rather than requiring a new model or orchestration stack.
Prerequisites: a running Docker/Podman engine and the runeward binary.
runeward quickstart
Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.
The command creates .runeward/quickstart.toml, checks the policy, runtime, image, and state path,
runs an allowed command, proves a destructive command is denied before execution, and verifies the
signed audit trail. It never overwrites an existing policy unless --force is passed.
doctor and dashboard readiness also resolve required secret sources. A Charter that references an
unset env:// value is not presented as launch-ready.
runeward doctor quickstart # explain setup problems safely
runeward --config-dir .runeward serve # dashboard + governed REST API
runeward evidence export quickstart -o run.json
runeward evidence verify run.json # independent policy/audit verification
Every governed action follows one path:
agent request → policy → human approval when required → limits → sandbox → signed audit event
Documentation and UI use familiar terms first. Existing API paths and file fields retain the original themed names for compatibility.
See the full naming and writing convention.
Choose the package that matches how you use Runeward:
For normal local use, install the CLI with Homebrew. For an agent integration, install the SDK for its language as well. The pip and npm packages connect to a running Runeward API; they do not replace the CLI/runtime.
Local sandboxes require a running Docker, OrbStack, or Podman engine.
brew install Runewardd/tap/runeward
runeward version
runeward quickstart
Requires Python 3.9 or newer. The base client has no third-party runtime dependencies.
python -m pip install runeward
python -c "import runeward; print(runeward.__version__)"
Requires Node.js 18 or newer.
npm install @runeward/sdk
npm ls @runeward/sdk
See Adapters for LangChain, CrewAI, LlamaIndex, OpenAI Agents, Strands, Vercel AI SDK, and LangChain.js installation options.
The signed macOS/Linux installer requires
cosign so it can fail closed while
verifying the checksum manifest. Windows binaries are available from
Releases.
curl -fsSL https://raw.githubusercontent.com/Runewardd/runeward/main/install.sh | sh
To build the current main branch, use Go 1.26.6:
git clone https://github.com/Runewardd/runeward
cd runeward
go build -o bin/runeward ./cmd/runeward
./bin/runeward version
Expose governed tools to an MCP-capable IDE or agent:
{
"mcpServers": {
"runeward": {
"command": "runeward",
"args": ["mcp", "--config-dir", ".runeward"]
}
}
}
Or place an agent CLI inside a sandbox and run one or many governed workers:
runeward cohort --agent claude --model sonnet build "Build a tested API"
Adapters are included for LangChain, CrewAI, LlamaIndex, OpenAI Agents, Strands, Vercel AI SDK, and LangChain.js. See Adapters and agent groups.
The dashboard also has a read-only Live chat TTY for each Citadel. Agent harnesses publish
user, assistant, tool, and system turns with runeward_publish_conversation (or the REST,
Python, and TypeScript equivalents), and authorized teammates can follow the redacted conversation
without terminal input access. Runeward cannot infer private UI chat text that the agent client does
not publish; wire the publish call into the harness turn callback. The publisher must connect to the
same runeward serve control plane as the dashboard (through /mcp, REST, or an SDK).
Runeward is the enforcement boundary around an agent, not the component that decides how the agent reasons. Route the tool calls of a parent agent and each delegated subagent through Runeward to give them explicit policy, approval, isolation, budget, and evidence boundaries.
Existing concepts keep their meaning: a Cohort is a group of peer workers sharing a task board; it is not being renamed to “subagents.” The orchestrator still decides when to delegate, while Runeward records the parent/run/provider lineage and prevents a child Citadel from widening its parent's tenant or Charter. Every participating agent can receive its own Citadel and Chronicle. See Agent harnessing.
Policies support built-in glob rules, CEL, OPA/Rego, and signed OCI bundles. Test them in CI, start from a reviewed scaffold, or derive exact proposals from verified production evidence:
runeward policy scaffold package-approval
runeward policy test quickstart --case 'tool=shell,action=rm -rf /,expect=deny'
runeward policy learn run.json > proposed-policy.toml
policy learn never edits a policy automatically. It verifies the evidence first, skips redacted
actions, produces exact matches, and requires a human to review and broaden them.
--allow-insecure-http explicitly acknowledges that a
trusted reverse proxy terminates TLS.RUNEWARD_ENABLE_EXPERIMENTAL_BROWSER=1 after reviewing the security model.
Browser-capable Charters declare capabilities = ["browser"]; the dashboard then exposes governed
rendered-text and screenshot actions and their policy/egress results.RUNEWARD_ENABLE_EXPERIMENTAL_IDE=1, Charter [ide], Dockerfile.ide targets
ide / ide-agents, examples ide-demo / ide-claude / ide-codex / ide-cursor.
Limits: not per-keystroke policy; no Cursor/Claude Desktop/Codex GUIs in-cell; no
first-class GitHub Copilot on code-server. See Browser IDE and the
security model.Contributions are welcome; see CONTRIBUTING.md. Licensed under Apache 2.0.
Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.
{ "mcpServers": { "io.github.runewardd-runeward": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/runewardd/runeward:v0.1.4" ], "env": { "RUNEWARD_CONFIG_DIR": "<value>", "RUNEWARD_STATE_DIR": "<value>" } } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
O publicador lista estas variáveis de ambiente: RUNEWARD_CONFIG_DIR, RUNEWARD_STATE_DIR.
Runeward roda localmente via stdio.
Última verificação: 2026-11-09. Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.