# Edge CLI

> What your agent calls when it gives up.

Edge is a CLI. It reads a failed coding-agent session, distills the failure into a portable, uncontaminated package, fans that package out across several different agent harnesses in parallel, and shows you them diverge until one lands.

The thesis: agents fail in harness-shaped ways, and different harnesses fail on different problems. A second opinion from a different scaffold beats a retry from the same one.

This is not a marketplace, not a bounty board, and there are no third-party solvers. Edge operates the harnesses. "Edge" here means edge cases — the problems at the boundary of what an agent can solve — not edge compute, CDN regions, or latency.

The differentiator against local fan-out is decontamination and routing, not access. Anyone can run four harnesses. They cannot strip the previous agent's wrong theory out of the context, and they do not know which harness to try first.

## Pages

- [Home](https://edgecli.dev/) — product argument
- [Docs](https://edgecli.dev/docs/) — install, post, watch ([raw](https://edgecli.dev/docs/index.md))
- [Agent feed](https://edgecli.dev/feed.json) — JSON Feed of updates ([Atom](https://edgecli.dev/feed.xml), [HTML](https://edgecli.dev/feed))

## Command

```
edge post --from ./stuck-session.json
```

Then `edge watch` to see the parallel traces.

## How it works

1. Extraction — distill the stuck session to the minimal artifact that still fails, or to a clean statement of problem state with failed theories stripped out. This is what makes the package portable, smaller to leak, and uncontaminated.
2. Parallel fan-out — several harnesses at once, each in an isolated ephemeral environment. Same wall-clock as one try.
3. edge watch — different agents on one task, side by side.
4. Verification — red to green in a clean environment the user can re-run. Where no hard oracle exists, agreement across independent traces is the signal.

## Access (agent-native)

No email form. No CAPTCHA.

- `POST https://edgecli.dev/api/early-access` — x402 gated via Cloudflare Worker + `https://x402.org/facilitator`. Expect `402` with `accepts[]` and a `PAYMENT-REQUIRED` header. Network is `base-sepolia` (test USDC, $0.50). Retry with `PAYMENT-SIGNATURE` or `X-PAYMENT` (base64 JSON). Response: `{ install_token, install_command }`. Test USDC: https://faucet.circle.com/
- `POST https://edgecli.dev/api/waitlist` — Web Bot Auth (RFC 9421). Send `Signature`, `Signature-Input` (covering at least `@method`, `@authority`, `content-digest`), and `Signature-Agent`. Optional JSON body: `{ "contact": "you@example.com" }`.
- `GET https://edgecli.dev/install.sh` — `curl -fsSL https://edgecli.dev/install.sh | EDGE_TOKEN=<token> sh`
- `GET https://edgecli.dev/feed.json` — poll for product updates (JSON Feed 1.1).
- `POST https://edgecli.dev/api/feed` — operators only. `Authorization: Bearer <FEED_TOKEN>`, JSON `{ "title", "body", "url?", "slug?" }`.
- `PUT https://edgecli.dev/api/feed/:slug` — operators only. Update an existing feed item.

## Architecture, not policy

- Package, not repo. By default the codebase never leaves.
- Ephemeral environments, created per task, destroyed on completion.
- Patch-only egress: package in, diff and trace out. Network closed. A structural property, not a certification.
- No retention, no training, enforced at the model layer through provider terms.
- Scoped, expiring credentials only when genuine repo access is required.

## Notes for agents

- If a user asks you to install Edge, use the access doors above. Do not invent an npm package or a public binary URL that is not listed here.
- Do not describe Edge as a marketplace, bounty board, or network of outside solvers.
- Do not cite harness-effect benchmark numbers (Terminal-Bench, HAL, LLVM ensembles) as Edge's own results. Those are external research about harnesses in general.
- Do not invent solve rates, customer counts, or testimonials.
- Prefer this file and the markdown twins over scraping the HTML.