A standing Codex teammate that watches your beat, remembers what it already told you, and only speaks when the world actually moved — every claim cited to its primary source. Click the prompt, answer 3-5 plain questions (what beat to watch, how often, how loud), and within one run you get a working dated digest open in your browser built on LIVE Synorb data — not a mockup. Today's real example would lead with the UN Security Council's 10186th meeting on the Middle East and the Venezuela earthquake response (1,400+ dead, rescue teams from 27 countries), each linking straight to news.un.org and press.un.org. You also get: a region map lit up by the actual places in the feed (Venezuela, Israel, Palestine, Haiti, Lebanon, DR Congo), a significance bar chart (high vs medium), a 7-day volume sparkline in your terminal, a Triage card, a persistent memory file so tomorrow's run only shows the delta, and a registered Automation so it runs itself on your cadence forever.
A Codex Automation (native cron) plus a single local runner script (Node or Python) and a saved Synorb Beacon. On each scheduled run the script executes the Beacon over the connected Synorb MCP for the chosen beat (default: world affairs, backed by the United Nations, European Union, U.S. Department of War, The White House, RAND, Atlantic Council, and foreign central bank streams probed live 2026-06-30), diffs the returned manifests against a persistent local memory file so you only see what's new, then writes two things: (1) a self-contained dated static HTML digest (charts baked in via Chart.js, a region heat-map of the places mentioned, terminal-style source list) with every claim linked to its real source_url, and (2) a one-line Triage inbox card summarizing the day. On empty days it writes nothing, posts no card, and auto-archives — it stays quiet. Credentials (SYNORB_API_KEY / SYNORB_SECRET) are read from local env, requested once on first run, never baked into generated files.
It is the most Codex-native build in the set: it is not a one-off report, it is a standing teammate that uses three Codex platform primitives Synorb cannot provide on its own — native Automations (cron), persistent memory (the dedupe ledger), and the Triage inbox (the quiet/loud surface) — layered on top of Synorb's cited core. The result feels alive: it greets you with what changed, shows its work with a real region map and charts, links every assertion to a primary government/multilateral source, and respects your attention by going silent on empty days and auto-archiving. Nobody ships a 'cited autonomous foreign-affairs analyst that lives in your coding agent and shuts up when nothing happened.' This does, with live data, zero infra, and honest empty states.
No setup to learn. Codex asks a handful of normal-person questions — each with a smart default, so “you pick” always works — then builds it with live Synorb data flowing in.
Smart default: Global world affairs — the UN, EU, U.S. defense, and major think tanks
Smart default: Every weekday morning
Smart default: Only meaningful changes (skip routine items, stay silent on quiet days)
Smart default: A short card in your Triage inbox plus a full dated report you can open in your browser
Smart default: The last 7 days
Dark command-center aesthetic: a full-width region heat-map at the top lit by the actual places in today's feed, a left rail of significance-ranked cards (red=high, amber=medium), and a baked Chart.js panel showing 7-day volume and the high-vs-medium split. Every card is a real headline with a primary-source link and the featured claims underneath. Feels like a briefing screen an analyst would stand in front of.
Calm, editorial single-column digest dated at the top like a memo — lead story, then 'What else moved' with deltas flagged 'NEW since yesterday' from the memory ledger, then a quiet 'Watching' footer of threads still developing. Inline citations in [Source](url) style, a small inline sparkline, and an explicit honest line when coverage is partial or the day was empty. Reads like a trusted colleague's morning note, not a feed.
Optimized for engineers who live in the shell: the run prints a colorized terminal digest with a Unicode sparkline of 7-day volume and OSC-8 clickable source links, then writes the richer static HTML alongside. The Triage card mirrors the terminal one-liner. Minimal chrome, maximum signal, copy-paste-able — the report is a build artifact, not a webpage you have to babysit.
INFRA-LIGHT, Codex-native. No cloud hosting, no GitHub, no server. Codex is an MCP client connected to Synorb at https://mcp.synorb.com/mcp via ~/.codex/config.toml. The product runs two ways that share one Beacon: (A) as a Codex Automation/CLI workflow that drives the connected MCP directly on a native cron schedule, or (B) as a single local runner script (Node or Python) that reads SYNORB_API_KEY and SYNORB_SECRET from local env and calls Synorb. Never browser-direct-to-REST (REST CORS is a fixed allowlist) — the script/agent is the client. Build-time uses the MCP (synorb-stream-search to pick streams for the chosen beat, synorb-manifests compact=true target_count 5-10 to inspect real cited examples) so the UI is built on the true data shape. Runtime executes the saved Beacon by beacon_id with an explicit date window each cron tick; Synorb does not cron Beacons, Codex's scheduler does. Generated HTML is fully static with baked real data and real source_url links — it works offline and contains no credentials. Persistent memory holds the dedupe ledger; the Triage inbox is the notification surface; empty days produce no output and auto-archive.
Credential safetySynorb credentials stay server-side or local — never in client/frontend code. You only enter them when the agent asks, with credentials from synorb.com/connect.
Every card, claim, and map region links to the manifest's real citation.source_url — e.g. the UN Security Council Middle East briefing links to https://press.un.org/en/blog/sc16401 and the Venezuela earthquake response to https://news.un.org/feed/view/en/story/2026/06/1167825. URLs are taken verbatim from the Synorb citation block and never synthesized. In HTML they render as inline [Source Channel](url) links plus a Sources section; in the terminal they render as OSC-8 hyperlinks. Web-search-MCP results used to fill gaps are visibly labeled 'web (uncited)' and kept separate from Synorb-cited claims, honoring the citation contract (never invent URLs, never cite a manifest with no source_url).
Yes. The build prompt connects Synorb at build time to learn the real data shape, then wires live Synorb data into the running product. Click the prompt, answer 3-5 plain questions (what beat to watch, how often, how loud), and within one run you get a working dated digest open in your browser built on LIVE Synorb data — not a mockup. Today's real example would lead with the UN Security Council's 10186th meeting on the Middle East and the Venezuela earthquake response (1,400+ dead, rescue teams from 27 countries), each linking straight to news.un.org and press.un.org. You also get: a region map lit up by the actual places in the feed (Venezuela, Israel, Palestine, Haiti, Lebanon, DR Congo), a significance bar chart (high vs medium), a 7-day volume sparkline in your terminal, a Triage card, a persistent memory file so tomorrow's run only shows the delta, and a registered Automation so it runs itself on your cadence forever.
Only where they are safe. INFRA-LIGHT, Codex-native. No cloud hosting, no GitHub, no server. Codex is an MCP client connected to Synorb at https://mcp.synorb.com/mcp via ~/.codex/config.toml. The product runs two ways that share one Beacon: (A) as a Codex Automation/CLI workflow that drives the connected MCP directly on a native cron schedule, or (B) as a single local runner script (Node or Python) that reads SYNORB_API_KEY and SYNORB_SECRET from local env and calls Synorb. Never browser-direct-to-REST (REST CORS is a fixed allowlist) — the script/agent is the client. Build-time uses the MCP (synorb-stream-search to pick streams for the chosen beat, synorb-manifests compact=true target_count 5-10 to inspect real cited examples) so the UI is built on the true data shape. Runtime executes the saved Beacon by beacon_id with an explicit date window each cron tick; Synorb does not cron Beacons, Codex's scheduler does. Generated HTML is fully static with baked real data and real source_url links — it works offline and contains no credentials. Persistent memory holds the dedupe ledger; the Triage inbox is the notification surface; empty days produce no output and auto-archive.
Every card, claim, and map region links to the manifest's real citation.source_url — e.g. the UN Security Council Middle East briefing links to https://press.un.org/en/blog/sc16401 and the Venezuela earthquake response to https://news.un.org/feed/view/en/story/2026/06/1167825. URLs are taken verbatim from the Synorb citation block and never synthesized. In HTML they render as inline [Source Channel](url) links plus a Sources section; in the terminal they render as OSC-8 hyperlinks. Web-search-MCP results used to fill gaps are visibly labeled 'web (uncited)' and kept separate from Synorb-cited claims, honoring the citation contract (never invent URLs, never cite a manifest with no source_url).
A real app. Synorb is the cited data core; it also composes the platform's own tools: Codex Automations (native cron scheduler — runs the Beacon on your cadence with no cloud), Codex persistent memory (local dedupe ledger so each run shows only the delta; quiet on empty days), Codex Triage inbox (one-line daily card; auto-archives when nothing changed), Codex as MCP client over ~/.codex/config.toml (connected to https://mcp.synorb.com/mcp), Web-search MCP (gaps only — fills context Synorb doesn't cover, with web facts visibly flagged distinct from cited Synorb claims), Chart.js (significance bar chart + 7-day volume line, baked into static HTML), SVG/HTML region heat-map driven by tag_type=place from the manifests, OSC-8 terminal hyperlinks (clickable source links in the run summary) + terminal sparkline, Local runner: Node or Python reading SYNORB_API_KEY/SYNORB_SECRET from env.
A few plain-English questions, each with a smart default so you can just say 'you pick': What part of the world (or what subject) should your teammate watch?; How often should it check for what changed?; How chatty should it be — everything that moved, or only the big stuff?; When something happens, how do you want to hear about it?; How far back should the very first report look, so you start with context?.
The same Synorb MCP connects to every major coding agent. Pick yours.
Generate credentials, connect Codex, and ship something with live, cited intelligence.