Session brief: an AI summary of the wire and the calendar
The session brief is a one-shot AI summary of what is currently loaded in the news terminal — the wire, the calendar and the instrument you picked. It opens as a drawer under the terminal, streams its text as it is written, and is thrown away rather than kept as a conversation.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- News terminal → Brief me, which opens the Session brief drawer
- Engine
- Whatever engine is configured on the AI page — Claude, Groq or a local model. The header reads "Written by {engine}" once the text is complete.
- Timeout
- 120 seconds; past that the drawer reports that the engine did not answer in time instead of staying in a reading state forever
- Storage
- None — the brief is not written into the AI thread history
What it does
Pressing Brief me builds a prompt out of the articles and events currently in the store, together with the symbol preset selected in the wire, and sends it to the configured engine over the same transport as the AI chat. The answer streams into the drawer, so text appears while it is being written. While the call is running the header shows "Reading the tape…" and the button is disabled, so a second brief cannot be started on top of the first.
Before it is run at all, the drawer is empty and invites a request: "Ask for a brief: the tone, what matters, the clock, your instrument." A brief can be run again at any time; each run replaces the previous text.
States and messages
| State | Trigger | What you see |
|---|---|---|
| Idle | Drawer opened, nothing run yet | The invitation line, and the Brief me button. |
| Running | A brief is in flight | "Reading the tape…" and the streaming text; the button is disabled. |
| Done | The engine finished | The full text and "Written by {engine}". |
| No material | Both the wire and the calendar are empty | "Nothing loaded yet — the wire and the calendar are empty. Wait for the feeds, then ask again." No call is made. |
| No engine | The error mentions a key, an engine or a model | "Set up an AI engine (Claude, Groq or local) in the AI page first." |
| Timed out | No answer within 120 seconds | An error stating that the engine did not answer in time. |
Why an empty terminal refuses a brief
The refusal on empty material is deliberate. A model handed no articles and no events will fill the gap — a scheduled release that does not exist, a central bank meeting invented out of nothing. Rather than let that reach the screen, the drawer declines, explains why, and leaves the button available for when the feeds have loaded.
Limits and pitfalls
- The brief only knows what is loaded. Articles are delayed by roughly fifteen minutes and the calendar window is two weeks, so the summary inherits both limits.
- A cloud engine sends the prompt to that provider, and any usage is billed by them under your own key. A local model keeps the text on the machine.
- The brief is a reading of the material, not advice and not a forecast. Nothing in it is a trade instruction.
Related pages
This page in other languages
Frequently asked questions
- Why does the button say I need an AI engine?
- No engine is configured, or its credentials were refused. Configure Claude, Groq or a local model on the AI page, then run the brief again.
- Is the brief saved?
- No. It lives in its own small store, is replaced by the next run and is not added to the AI conversation history.
- Does the brief see my chart or my positions?
- No. It is built from the loaded articles, the loaded events and the symbol preset chosen in the wire.