Conduit.
Running real code from a source you decide to trust should take one click, not a terminal.
- Status:
- prototype (Preview, closed alpha)
- Built with:
- TypeScript, Swift
- Licence:
- Apache-2.0
What it is
Conduit is a local runtime plus transports for running code on your own machine, with a trust model: you know who is asking.
Sources you trust, a paired session, run quietly. An unknown source asks you once. Every call carries a one-shot nonce, so a request cannot be replayed.
The thesis
Running real code from a source you decide to trust should not stay a power-user skill. The aim is one click: no installer, no terminal.
Conduit is not a safety product, not a sandbox and not an auth bypass. It is arbitrary code execution on your machine, and the consent model is how you stay in charge of it.
What works today
- A TypeScript CLI and runtime with a policy engine, a session and nonce store, local tools and run logs.
- A control panel on 127.0.0.1 with approvals and a demo-data mode labelled as such.
- A macOS menu-bar app that supervises Conduit's local services and stops them when you quit.
- A clipboard daemon that acts only when the whole clipboard is one exact Conduit request (macOS clipboard).
- Permission profiles from read-only to shell-with-approval. Approvals expire after 10 minutes, and a timeout means deny.
- A pause switch that every execution path checks before any tool runs.
Limitations and scope
- A preview: v0.0.1 is a closed-alpha build.
- The macOS app is not code-signed or notarized by Apple, so macOS warns on first launch.
- No clipboard support on Linux or Windows, no native Linux or Windows tray apps, and no Chrome Web Store listing for the extension yet.
- Sandboxed dry runs and trust analysis for higher-risk requests are not built.
- The one-click “Start a server” flow is a direction, not built yet.
Source
The code is public. Everything on this page comes from Conduit's own README; the README is the place to check what has changed since.