Set up a stream with the assistant (experimental)
Stream setup is experimental in 0.16.0. An assistant reads a context stream you have already registered, asks you whatever it cannot work out, and proposes how the stream should be set up. A proposal changes nothing until an administrator approves it. The assistant can be wrong: read each proposal before you approve it, and ask the stream's verification questions once it has run.
It is on by default. Only a super administrator can open it, from Admin → Stream setup (experimental). The chat everyone else uses never gets its tools.
What it can do
The page offers two modes. It picks the right one from how the stream was registered.
| Mode | For | What the assistant proposes |
|---|---|---|
| Customise a recipe | a stream registered from one of Prism's recipes that leaves settings open: today GitHub, GitLab and Jira | values for those settings only: which organisations, groups or projects to cover, how far back to start, which Jira fields hold story points |
| Describe from scratch | a query-through stream (Snowflake, Oracle) registered with a starting document | a complete document: its tables and views, a few sample rows, which date columns actually move. It asks you about look-alike tables instead of choosing one. |
Not available yet: describing a mirror or snapshot stream from scratch. The page refuses to open that session, and marks a mirror or snapshot stream you wrote the document for "from-scratch not available yet". A mirror or snapshot stream registered from a recipe can still be customised if its recipe leaves settings open. To author one of those by hand, use the Manifest tab, as in Copy a Postgres table or view.
The database and file recipes (the Snowflake, Clarity and Postgres ones, and the people file) leave nothing open to a session: every setting they declare says where the data is, who signs in or how the session is set up, and those are yours; change them on the stream's own page. A query-through stream registered from one of them opens in Describe from scratch instead, and the page marks the others "nothing to customise".
Before you start
- Register the stream first, with its credential. The assistant only works on a registered stream, using the credential stored on it. It never asks you for a host, a login or a password, and it cannot reach any host but the one you registered.
- Open Admin → Stream setup (experimental), pick the stream, and say what you want in your own words, for example "we only care about the platform teams' projects".
The assistant runs on your Agent Router like the chat does, so a session costs Router tokens. Each turn has a fixed allowance of requests and of data read from your system.
Approving a proposal
A proposal shows what would change against the stream as it is now: the changed settings for a customise proposal, or a line-by-line difference for a document. Nothing is written until you press Approve.
- A customise approval writes those settings and nothing else. The stream keeps its document, its credential and its state. Its verification answers are reset, because its figures now cover something else, so ask the questions again once it has run. A proposal that sets the values the stream already has is refused rather than approved.
- A document approval goes through the Manifest tab's own apply, with the same checks and the same outcome, which the approval repeats: a change to the model needs probing, approving and enabling again, like any edited manifest; a change only to how the stream is labelled keeps its state.
- A proposal made before the stream changed is refused. If someone edited the stream's settings or document after the assistant proposed, approval says so and writes nothing. Ask the assistant again.
- A proposal can't move the stream to another host, change who it signs in as, or change what kind of stream it is.
Switching it off
Set mcps.discoveryMcp.enabled: false in your values and upgrade. The
assistant's pod and the Stream setup page both go, and nothing else changes.
It is also off whenever sources.registry.enabled is off, because it has
nothing to read without the registry. The image is discovery-mcp: mirror it
with the others, as Installing Prism lists.