Skip to content
deLiseLINOPublic

About

Prism desktop and local daemon

Resources

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

prism

Local proxy with a terminal UI, a CLI and a desktop app.

Install

Homebrew (macOS, Linux)

brew install deLiseLINO/tap/prism

Go 1.27 or newer (macOS, Linux, Windows)

go install github.com/deLiseLINO/prism/cmd/prism@latest

Archive. Download prism_<version>_<os>_<arch> from the releases page, unpack it and put prism on your PATH.

Desktop app. Installers for macOS, Windows and Linux are on the releases page. On macOS: brew install --cask deLiseLINO/tap/prism-desktop.

Use

prism                 # start the daemon if needed and open the UI
prism status          # CLI commands, see `prism help`
prism service stop    # stop the background daemon
prism upgrade         # update prism (brew and go installs)

The daemon listens on 127.0.0.1:10200. The UI, the CLI and the desktop app share it.

Anthropic Messages requests retain client cache_control markers and system block boundaries when routed to a Messages provider. No additional settings are required. Prism does not add cache markers to requests that omit them.

Chat providers may send tool_calls: null in stream chunks. Prism treats it as no tool-call update and preserves text and active tool calls. Non-null tool-call values must still be arrays.

Within streamed tool calls, null id, name, and arguments fields mean no update. Prism preserves the call identity and accumulated arguments. Non-null values in these fields must still be strings.

When a Chat provider stops with finish_reason: "length", Prism preserves the output-limit reason, text, reasoning, and token usage. It does not finish tool calls from that turn. Non-streaming responses omit those calls. Streaming clients may have received partial tool deltas and must not execute them after a length stop. Malformed tool arguments on normal completion still fail.

Provider HTTP failures retain their original status on non-streaming responses, their error details, and plain-text messages. An unavailable fallback does not replace an earlier provider failure. A rate or quota refusal takes precedence over a later authentication refusal before output begins.

After a provider rejects a credential, prism retains that refusal for later requests in the running daemon. Replacing the credential or resuming the account clears it. After a daemon restart, an account that still needs login receives a local login-required message instead of a quota error. Missing, paused, and unselected accounts return account_unavailable, not quota_exhausted.

About

Prism desktop and local daemon

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Contributors

Languages