Local permissions for AI assistants
SEED Clearance
Let an AI assistant act without giving it unlimited access. SEED gives the assistant a local identity, a signed permission slip, a sandbox budget, a signed activity log, proof you can verify, and a revoke switch.
Keep your assistant. Decide what it may do. Prove what happened.
curl -fsSL https://seedid.xyz/install.sh | sh
seed clearance setup
Connects to Claude Desktop·Cursor·Continue·any MCP-compatible assistant.
Local control-plane testing is available. seed-clear P2/P3 is live on Earth; A3-G4/G7 now has bounded chain evidence and a hosted proof page. Payout, claim actions, hosted rewards, and private payment remain gated.
What happens when you run setup
SEED turns an assistant into something you can authorize, inspect, and stop.
You keep using the assistant you already know. SEED adds the local control layer around it: who it is, what it may do, what it did, and whether it is still allowed to act.
step · 01
Install SEED
download a signed local tool
step · 02
Create your identity
make a local key and policy
step · 03
Connect your assistant
Claude, Cursor, Continue, or MCP
step · 04
Approve an action
let the agent do one allowed thing
step · 05
Record what happened
write a signed local receipt
step · 06
Export proof
show what the agent did
step · 07
Revoke access
stop the agent immediately
Step: Install SEED
◆SEED checks the rule before the assistant gets a result.
Downloads the SEED command line tool and checks that the files match the signed release. If the signature or checksum is wrong, it stops.
curl -fsSL https://seedid.xyz/install.sh | sh
What you can see
Commands can print a readable view for humans. Under the hood, the proof format is deterministic and verifiable.
human-readable receipt
SEED installed. Signature checked. Ready for setup.readablesignedlocalinstall
Current availability
Current wave gates stay explicit.
P2/P3 clearance verification is public-live. A3-G4/G7 now proves the bounded chain bridge and hosted economic proof surface, but `MsgClaim`, wallet payout, hosted rewards and private-payment rails still wait for their own evidence.
Local setup
available
P2 runtime
live
P2/P3 API
live
R1/P6/P7
G4/G7 done
W7 privacy
hold
Plain answers
What a new user should know first
Do I replace my assistant?
- No. Keep Claude Desktop, Cursor, Continue, or another MCP assistant.
- SEED runs beside it as the local permission layer.
- The assistant asks SEED before using controlled tools.
What do I get?
- A named assistant identity.
- A clear permission slip and sandbox budget.
- A signed record of what happened.
- A proof file and an immediate revoke command.