DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to build a custom frontend on the Bridge protocol with Nosis

Drive the Nosis runtime from your own program over newline-delimited JSON on stdio.

Who it is forA developer building a custom interface, script, or integration that needs to control a Nosis agent programmatically.

The problemExisting Nosis frontends do not fit a custom workflow, and the runtime has to be reachable from another process.

The outcomeA client program that launches the Bridge, sends requests, and receives agent events through the public protocol.

What you need first

  • Python 3.11 or newer
  • Node.js 22 or newer
  • uv installed
  • An API key for the default provider, such as OPENAI_KEY

Steps

  1. Read docs/bridge-protocol.md in the Nosis repo to learn the public stdio protocol and message shapes.
  2. Read interfaces/client/README.md for the lightweight TypeScript client and its process lifecycle example.
  3. Launch the installed nosis-bridge command as a child process from your program.
  4. Send newline-delimited JSON requests on the Bridge stdin and read its events from stdout.
  5. Handle frontend interaction requests, such as approvals, so the agent can continue.

Prompt for your agent

Using the Nosis repo at https://github.com/EvannZhongg/Nosis, read docs/bridge-protocol.md and interfaces/client/README.md, then write a minimal script that launches `nosis-bridge` for <target workspace>. Output the first event the Bridge returns and the list of message types you used. Verify that the script shuts down the Bridge process cleanly.

Caveat. The README says the public protocol and internal Bridge messages are separate, so build only on the documented public protocol and not on internal message types.

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer