ai-radar
Every morning at 9, a headless agent sweeps the AI landscape through six parallel lenses — and publishes only the part that's safe to show you.
Every morning a bot reads the day's AI news across six angles and writes me a private briefing. This page is the public, headlines-only slice of it — regenerated automatically each morning, with everything personal stripped out.
Run it live
embedded · interactive- Claude Opus 4.8 + Dynamic Workflows
agentic coding 64.3%→69.2%, more honesty about uncertainty, fast mode ~2.5× faster/3× cheaper; Dynamic Workflows moves the orchestration plan
winbuzzer.com - Cursor Composer 2.5 / Windsurf SWE-1.5
Composer 2.5 matches Opus 4.7/GPT-5.5
shareuhack.com - GitHub trending: claude-context, pi-mono, ml-intern askglitch.com
- Both labs spin up enterprise "deployment companies"
the FDE model goes institutional at the billion-dollar level, premised
techcrunch.com - Gartner: uniform governance will cause AI agent failure
govern by autonomy/scope, not a binary
gartner.com - AI regulation fragments into three independent fronts
copyright (CNN sued Perplexity May 28; 9 publishers now litigating), federalism (DOJ-backed xAI v. Colorado AI Act), EU/CA transparency
techtimes.com - EU AI Act "Digital Omnibus": high-risk deadline slips to Dec 2027
~16-month reprieve + SME relief
globalpolicywatch.com
How it works
tap a node · drag + zoomThe ideas behind it
tradeoffs, statedThe run is the unit of work — it has a clear start, a token and wall-clock budget, and a full log. A scheduled sweep that fails pings me on its own; I don't have to remember to ask it anything. No always-on swarm, no chat session to babysit — just a result on the vault every morning before I'm at the desk.
Each lens has a different intent — releases, practitioner chatter, business, gaps, news, craft — so each is independently tunable and runs in parallel. The hard rule across all of them: every item links a real source. The lens that hunts unmet needs is the one that turns a news feed into a wedge list.
The full brief is deliberately personalized — it names projects, strategy, and priorities, which is the whole point of it being useful to me. So the public surface is a deliberately narrowed projection: a deterministic backstop reads only the external Releases and News lenses, strips the personalized editorial from each item, and drops anything that still names a private project against a denylist — then aborts the write entirely if a flagged token survives.
The digest isn't a throwaway feed — it's connected knowledge. Each run wires itself into the vault graph with bidirectional links and drops a backlink into the tracker of every project it touched, so a signal from this morning is one hop from the work it affects.
The brief I actually read every morning is full of things I’d never put on a public page — which project a signal feeds, what it’s worth, what I’d build next. That’s not a problem to scrub away after the fact; it’s the design constraint up front. The public surface is a separate, deterministic projection of the run: it reads only the external lenses, strips the personalized framing, and fails closed if anything private survives. Same discipline as the rest of this site — the safe version is built, not bolted on.