·Dashboard for Open Wallet Standard 🐕
Built on Open Standard v1.0.0

A cool dashboard
for Open Wallet Standard.

OWS handles the policy engine, key management, and signing. LEASH gives it a face — register your agents, configure spend limits, restrict chains, and watch every transaction in real time. Keys never leave ~/.ows/.

AgentsYour Claw, Claude Code, Codex, or any other agent can manage wallets here. Copy the install prompt and paste it into your agent to get started.
How it works

OWS does the heavy lifting.
LEASH makes it visible.

OpenWallet Standard handles policy enforcement, key security, and transaction signing. LEASH is the dashboard that lets you configure and observe all of it — no terminal required.

01
Register your agents
Add each agent to LEASH. It gets its own OWS wallet and a scoped API key — no raw keys ever leave your machine.
02
Configure spend rules
Set a daily budget per agent. Restrict which chains it can use. Add vendor allowlists. OWS enforces every rule before any key is touched.
03
Connect your agents
Drop the API key into your agent's environment. When it needs to transact, it calls your local LEASH instance — OWS signs and returns the transaction.
04
Watch and control
Every transaction attempt appears in real time. See what was approved, what got blocked, and why. Pause any agent instantly from the dashboard.
Get Started

Up in 30 seconds.

Clone the repo, install, and run. No accounts. No cloud. Everything runs locally on your machine.

Bring your agent into LEASH

Your Claw, Claude Code, Codex, or any other agent can manage wallets here. Copy one prompt that tells it to connect first, read wallet state next, and install only if needed.

You are about to install and use LEASH — the local dashboard for Open Wallet Standard (OWS). Follow every step in order.

STEP 1 — Install LEASH:
Run these commands in your terminal:
  git clone https://github.com/Socialure/leash
  cd leash/app
  npm install
  npm run dev
Wait until you see "Ready on http://localhost:3847". Then confirm with: curl http://localhost:3847/api/agents

STEP 2 — Register yourself as an agent:
Open http://localhost:3847 in a browser (or use the API directly):
POST to http://localhost:3847/api/agents with JSON body:
  { "name": "<your agent name>", "role": "<your role>", "spendLimit": 100, "chains": ["eip155:8453"] }
Save the "id" and "apiKey" fields from the response — you will need both.

STEP 3 — Use your wallet:
To simulate or sign a transaction, POST to http://localhost:3847/api/simulate:
  { "agentId": "<your agent id>", "chain": "eip155:8453", "amount": 10, "action": "swap" }
LEASH will approve or deny based on your spend policy. Raw keys never leave the vault.

STEP 4 — Report back:
Confirm: your agent name, wallet ID, spend limit, allowed chains, and API key (first 8 chars only). If any step failed, report the exact error message.
1
Clone and start LEASH
LEASH and OWS core install together. Dashboard opens on localhost:3847.
git clone https://github.com/Socialure/leash
cd leash/app
npm install
npm run dev
# Then open localhost:3847 in your browser
2
Register your first agent
Click “Register Agent” in the LEASH dashboard. Set a name, daily spend limit, and chain allowlist. LEASH creates an OWS wallet and issues a scoped API key.
# Or use the OWS CLI directly
ows wallet create --name agent-treasury
ows policy create --wallet agent-treasury \
  --limit 100 --chains eip155:8453
3
Connect your agent
Add the API key to your agent's environment. It signs through your local LEASH instance — raw keys never leave the vault.
// Node.js — @open-wallet-standard/sdk
import { OWSClient } from '@open-wallet-standard/sdk'

const ows = new OWSClient({ apiKey: process.env.OWS_KEY })
const { txHash } = await ows.sign({
  chain: 'eip155:8453',       // Base
  to:    '0xrecipient',
  value: '0.01',
  unit:  'eth'
})
Features

Every OWS capability.
One clean interface.

LEASH doesn't replace OWS — it exposes it. Every feature you see maps directly to an OWS primitive. The standard does the work; LEASH makes it accessible.

01
Local-first
LEASH runs on your machine. Your OWS keys stay in ~/.ows/ — not in a browser extension, not in the cloud.
~/.ows/wallets/
02
Visual spend tracking
See exactly what each agent spent, which transactions were blocked, and why — all without touching a terminal.
Real-time dashboard
03
Per-agent policies
Each agent gets its own spend limit, chain allowlist, and API key. Change or revoke any of them in two clicks.
Per-agent keys
04
Instant pause
Something looks wrong? Freeze any agent immediately from the dashboard. Transactions stop at the policy layer — no on-chain action required.
One-click control
05
Multi-chain
One LEASH instance manages wallets across ETH, Base, Solana, and more. Configure which chains each agent is allowed to use.
8 chains
06
Composable by design
LEASH adds a UI layer — the OWS CLI, MCP server, SDK, and REST interfaces still work exactly as documented.
MCP · SDK · CLI · REST