Porta

Run an agent with the permissions you actually granted it.
OS-enforced limits for the CLI agents you already use, and a WASM runtime for the ones you build.

Almide + Wasmtime · No Docker required

English · 日本語

---

Who this is for

• You run a CLI agent and want it unable to write outside one directory or reach hosts you did not allow — enforced by the OS, not by a prompt.
• You hand agents to a team and need a record of where they tried to connect.
• You build agents and need a run that can be resumed after a crash without repeating work, and a completion check the agent cannot talk its way past.

If none of these are your problem yet, Porta will not be interesting. It is a runtime and a set of restrictions, not an agent.

Install

bash scripts/install-almide.sh
.tools/almide/almide build src/mod.almd -o target/porta
cp target/porta ~/.local/bin/

Needs Almide 0.63.0, a Rust toolchain, Python 3 and curl. Full verification steps and the compiler pin are in [Build from source](#build-from-source).

Quick Start

1. Restrict an agent you already use

porta run claude --allow-net 'api.anthropic.com:443' -v ./project -e "HOME=$HOME" \
  -- --print "Fix the bug in main.rs"

`claude` runs normally, but it can write only inside `./project` and connect only to the host you listed. No Docker daemon, no container image, no change to the agent itself.

2. See a restriction actually stop something

A working restriction is invisible, so watch one fail:

porta run curl -- https://example.com                    # network open by default
porta run curl --allow-net '*:443' -- https://example.com # HTTPS allowed →