mirror of
https://github.com/AgentSeal/codeburn.git
synced 2026-07-10 09:39:24 +00:00
887374de2c
* feat(sharing): pairing, token, and device-identity core First piece of local device sharing: self-cert fingerprint identity (trust-on-first-use), a one-time expiring pairing PIN, fingerprint-bound tokens, and a peer store that authorizes a pull only when both the token and the TLS peer fingerprint match the same paired device. Pure logic, fully unit-tested; the TLS share server and host pull build on this. * feat(sharing): secure mutual-TLS transport + pairing handshake Add device identity (self-signed cert, persisted; fingerprint = sha256 of the cert DER), an HTTPS share server (mutual TLS: presents its cert, reads the client's, and serves /api/usage only when the bearer token AND the client fingerprint match the same paired peer), a one-time-PIN pairing endpoint, and a fingerprint-pinning client. Verified end to end on loopback: PIN pairing, pinned authed pull, and rejection of a wrong PIN, a token replayed from another device, and a mismatched server fingerprint. Adds the selfsigned dep (Node cannot generate certs natively). * feat(sharing): share + devices CLI (pair, pull, combine) Phase 3 terminal flow: codeburn share runs the secure server on-demand (stops after 10 min idle; --always to persist, --pair to add a device), and codeburn devices add <host> --pin <pin> pairs and pins a remote. codeburn devices pulls this machine plus every paired device, keeps each separate, and prints a per-device table with a simple summed Combined row (no server-side merge). Persists identity and peers under the config dir. Host pair-and-pull flow covered by a loopback integration test. * feat(sharing): mDNS discovery + approve-style (no-PIN) pairing Add bonjour-service discovery (advertise/browse over the LAN), a short confirmation code derived from both cert fingerprints (Bluetooth-style 'do these match?' check), and an approve-style pairing endpoint that prompts the owner instead of requiring a typed PIN. Loopback-tested: approved device gets a working token with a matching code on both sides, declined device is rejected. * feat(sharing): AirDrop-style discover + approve UX codeburn share now advertises on the LAN and approves incoming devices interactively (confirm the matching code, no typed PIN). codeburn devices add (no args) discovers nearby devices, lets you pick one, shows the confirmation code, and waits for the owner to approve. Manual add <host> --pin stays as a fallback for networks that block mDNS. * feat(sharing): share only aggregates, never project names or paths Sanitize each device's payload before it leaves the machine: drop topProjects and topSessions (project names + session detail) and send only aggregate numbers (cost, tokens, models, tools, activities, daily). What you are working on stays local; only the totals travel. |
||
|---|---|---|
| .. | ||
| data | ||
| mcp | ||
| providers | ||
| sharing | ||
| antigravity-statusline.ts | ||
| bash-utils.ts | ||
| classifier.ts | ||
| cli-date.ts | ||
| cli.ts | ||
| codex-cache.ts | ||
| codex-credits.ts | ||
| compare-stats.ts | ||
| compare.tsx | ||
| config.ts | ||
| content-utils.ts | ||
| context-budget.ts | ||
| currency.ts | ||
| cursor-cache.ts | ||
| daily-cache.ts | ||
| dashboard.tsx | ||
| day-aggregator.ts | ||
| export.ts | ||
| fetch-utils.ts | ||
| format.ts | ||
| fs-utils.ts | ||
| ink-win.ts | ||
| main.ts | ||
| menubar-installer.ts | ||
| menubar-json.ts | ||
| model-efficiency.ts | ||
| models-report.ts | ||
| models.ts | ||
| optimize.ts | ||
| overview.ts | ||
| parser.ts | ||
| persistent-codeburn.ts | ||
| plan-usage.ts | ||
| plans.ts | ||
| session-cache.ts | ||
| sqlite.ts | ||
| types.ts | ||
| usage-aggregator.ts | ||
| web-dashboard.ts | ||
| yield.ts | ||