Save this key somewhere safe — it is how you get back into this desk on another device, and nobody can show it to you again once you sign out.
Your invite link — when a friend creates their desk through it, the mesh records that you brought them (you earn spend-only MESH only if they become a real, active member — never for a signup):
Your DevDesk
A private workstation for building with agents — a sealed vault, a webhook inbox, drafts that
publish to the market, and a brain to think with. Free to start.
You were invited — creating your desk records who brought you.
One tap. No key to copy, nothing to install — you land right in your desk.
The email is optional: the market keeps only a one-way hash of it, and uses it for nothing but a recovery link you ask for.
THE BRAIN — remembers your work, strategizes the next listing
Each exchange rents agent-brain on your key and settles on the market. Your memory here is permanent until you clear it.
THE BENCH — drafts, committed and pushed
WALLET & LEDGER — every credit in and out, itemized
Reading your ledger…
THE TESTER — fire one real capability call by hand, with the receipt
Pick anything listed, fill its declared inputs, fire one real call. You see the exact request, the raw response, and what it cost — nothing is simulated: this is the same POST /api/call/:slug an agent uses, settled the same way, on your key.
Loading the catalog…
WHAT YOU SELL — your listings, active and unlisted, with their receipts
Reading your listings…
KEYS — this desk's key, delegated sub-keys, and your way back in
Reading your keys…
EVENTS — your node's live events, POSTed to an endpoint you own
Reading your subscriptions…
THE MARKET NOW — live, keyless, house volume counted apart
Reading the mesh…
THE SCOUT — send an agent to a page you can't reach, come back to the answer
A real headless browser loads the page (JavaScript runs, so JS-only and
region-walled pages work where a plain fetch returns nothing), then the agent does what you
asked with what it found. Dispatch it and leave — the result is saved here either way.
Straight answer on the limit: the browser is always identifiable as a bot, so a site running
active bot-management can still refuse it. Analysis rents agent-brain on your key.
DISPATCH LOG
THE CONNECTIONS — save a token once, every agent reads it (never the raw value)
Each service is one row. Key-based services (Twilio, Supabase, Cloudflare, model keys) post a small form straight to the desk; Stripe and GitHub open a consent screen. Every secret is sealed before it touches storage — agents call by capability, never the value. Money-moving capabilities do not exist here.
TEST A CAPABILITY
THE AGENTS — pick one, bring it up, own it fully
A ready helper, a small local model that fits a normal laptop, its wake-up prompt baked in. Bring it up your way: one file for your machine, Docker compose, a cloud-init for any VM, or a Dockerfile for Railway/Fly. The model, the prompt, and every conversation stay on the machine you run it on — free, and yours.
THE SANDBOX — every endpoint and webhook, before it goes live
TEST-FIRE AN ENDPOINT
https only · private, loopback and link-local hosts refused · redirects are reported, never followed with a secret aboard · once a {{VAULT:...}} value is expanded the response body is withheld, and it may not be fired at this desk
WEBHOOK INBOX
Point any external service at your private capture URL. Every delivery lands below for inspection — signatures, headers, body.
IDEA TO WORKING SOFTWARE
You bring the idea. Your agent handles the details.
Describe the result you want. Prepare a brief, keep it on your desk, and give your browser agent a clear place to start.