Keep up with your agents. Spotlight reads your Claude Code and Codex sessions and shows you what your agents actually did, and how to get recursively better every session: what to fix now, what to ship better next time, what's worth sharing. One harness or seven, solo or across your team. Free.
Hey Product Hunt. We're Seth, Neil, and Nick, and we've spent a decade in security and dev tools across Google/Gmail, Valimail, Twilio, and Algolia.
We built Spotlight by Backplanes to help you keep up with your agents. It reads your Claude Code and Codex sessions and shows you what your agents actually did: session reports that make you a better engineer, every day.
This started with a scare. Neil asked Claude to fix one file. It read 47, including his ~/.ssh keys, and wrote an API key into a tracked .env. We build security software, and our own agents did this. We missed it, and caught it by accident while investigating something else.
So we looked deeper, stitching our Claude and Codex sessions together across machines. Two things floored us: how much we'd missed, and how many good moves we were making in one place but not another. Surfaced and shared, those patterns made us better, every day.
That's what Spotlight does for you. After every session, you get a report: what to fix now, what to ship better next time, what's worth sharing. One harness or seven, solo or across your team.
We're building toward a world where you can see and manage everything your agents do. Visibility is where it starts, and we think everyone deserves to know what their agents are doing, so we're making this piece free. We'll be offering paid features and automations in the near future; seeing what your agents did won't cost you. Private and secure by design, with details at backplanes.com/trust.
Install is one line, and your first report lands in ~2 minutes: Get started on backplanes.com.
300$ for 50min coding. what kind of models are you running? 😅 How does it get recursivly better for each session i dont get it? reminds off entire.io
This is a useful direction. For coding agents, the hard part is usually not generating more code, it is making the session reviewable afterward.
The report I’d want is pretty boring: changed files, risky assumptions, tests/checks run, failed attempts, and a short “what a human should look at first” section.
The OS-level instrumentation approach is smart. It captures what agents actually do rather than what they report back. We've run into exactly this problem: an agent silently inlining an API key when it couldn't find the env var, and that key landing in git history. How do you distinguish intentional credential usage in test fixtures from actual leakage?
The "what your agents actually did" angle is great, that read-47-files scare is too real. When you're running several harnesses at once, does Spotlight give you one combined report or one per session?
The scary part of vibe coding fast isn't the bug you catch, it's the secret you committed three sessions ago and never noticed. I spent years in risk and security before I ever touched Claude Code, so "what my agent actually did" is exactly the report I always wished I had. Does Spotlight call out the security stuff specifically, leaked keys, missing checks, or is it more about code quality and patterns?
Well done! Was post-session reporting a deliberate call over an inline guardrail that interrupts the agent mid-write (i.e. less intrusive, keeps you in flow)?
You emphasize “no OAuth into Anthropic/OpenAI” and still show org-level rollups (security/engineering/spend) with spend reconciliation close to invoices. How are you attributing sessions and spend across engineers/repos/tools without provider-side integrations, and what were the key tradeoffs you made to ship that early versus, say, real-time monitoring or policy gating?
Hey congrats on the launch!
This looks really promising. I’ve had way too many Claude sessions where I come back after a break and have no clue what just happened in the project. The automatic capture + those session summaries with the “needs review” flags feel like such a sanity saver.
The session report angle makes sense. What I'm curious about is how much signal you're actually extracting versus just replaying what happened. Claude Code sessions can get noisy fast, lots of back-and-forth, abandoned branches, retried prompts, and the raw transcript isn't that useful without some layer of interpretation on top. Does Spotlight surface things like where the agent got stuck, or which tool calls failed silently, or is the report mostly a structured summary of the final output? Also curious what the security topic covers here, whether you're flagging things like secrets exposed in prompts or risky code patterns the agent introduced, since that would be a genuinely different use case than the reporting side.
Love this! As an enthusiastic-but-amateur engineer, this is super useful. The rapid evolution of coding agents are like katanas; incredibly powerful tools when used correctly. Wield them wrong and you'll cut your own arm off (I've done it many times). Having an expert keep tabs on ensuring both me and my agent(s) aren't going off-piste is critical.
Looking forward to see how Spotlight and Backplanes evolve.
Congrats @antifreeze - this is one of those products that feels obvious once you see it.
I’m using Claude Code/Codex every day right now, and the trade off is you don’t really know what got touched, what got skipped, or what weird security debt just got created. In our space making sure everything is tightened up and polished is a necessity more than ever.
Spotlight makes it clear what actually happened. Every team using agents seriously is going to need this. Bullish.
There’s a tension right now between allowing your team to adopt cutting edge AI tools & maintaining good security practices. Backplanes is solving that so you can move fast without compromising on security.
Seth, Neil and Nick are the perfect team to be building this product and I’m thrilled to be an early tester and customer.
As of this year, I’ve become a “non-engineer engineer”, letting Claude and all his robot friends abuse my terminal. For example, the other day I just discovered how to actually use a `.env` file. Yes, I am embarrassed.
How was I forced to discover this? @antifreeze (who I've known for what? 20 years??) gave me a demo of Backplanes and in a reports on one of my coding sessions I saw red:
And this wasn't the only red I saw...!
Backplanes showed me the ugly underbelly of my agent sessions: leaked credentials, missing tests, sloppy patterns I’d normalized because the app I was building "worked".
By shipping like a maniac, I leaked my secrets all over the place — and Backplanes provided me actionable steps to get my shit locked down.
This isn't just “agent analytics.” It’s a backstop for the bullshit your coding agents quietly create while you’re moving at AGI speed. Like being shown what bacteria lives on your toothbrush when you stop to under a microscope. 🦠🤮
So if you haven't been practicing excellent agentic hygiene, give Backplanes a try.
Because behind every successful coding session is a backplane.
Some recent discussions here pointed out that using a terminal like @Claude Code might feel too "zoomed out" from the code. Many prefer to stay in the loop and see what their agents are actually doing. [1]
@Spotlight by Backplanes fixed just that. It brings clarity to your agentic coding sessions and, more importantly, it compounds, making you a better engineer every session.
“Session reports for Claude Code & Codex to improve your code”
Spotlight by Backplanes launched on Product Hunt on June 10th, 2026 and earned 179 upvotes and 36 comments, earning #3 Product of the Day. Keep up with your agents. Spotlight reads your Claude Code and Codex sessions and shows you what your agents actually did, and how to get recursively better every session: what to fix now, what to ship better next time, what's worth sharing. One harness or seven, solo or across your team. Free.
Spotlight by Backplanes was featured in Developer Tools (513.7k followers), Artificial Intelligence (470.5k followers) and Security (2.7k followers) on Product Hunt. Together, these topics include over 175k products, making this a competitive space to launch in.
Who hunted Spotlight by Backplanes?
Spotlight by Backplanes was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Spotlight by Backplanes stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian
Hey Product Hunt. We're Seth, Neil, and Nick, and we've spent a decade in security and dev tools across Google/Gmail, Valimail, Twilio, and Algolia.
We built Spotlight by Backplanes to help you keep up with your agents. It reads your Claude Code and Codex sessions and shows you what your agents actually did: session reports that make you a better engineer, every day.
This started with a scare. Neil asked Claude to fix one file. It read 47, including his ~/.ssh keys, and wrote an API key into a tracked .env. We build security software, and our own agents did this. We missed it, and caught it by accident while investigating something else.
So we looked deeper, stitching our Claude and Codex sessions together across machines. Two things floored us: how much we'd missed, and how many good moves we were making in one place but not another. Surfaced and shared, those patterns made us better, every day.
That's what Spotlight does for you. After every session, you get a report: what to fix now, what to ship better next time, what's worth sharing. One harness or seven, solo or across your team.
We're building toward a world where you can see and manage everything your agents do. Visibility is where it starts, and we think everyone deserves to know what their agents are doing, so we're making this piece free. We'll be offering paid features and automations in the near future; seeing what your agents did won't cost you. Private and secure by design, with details at backplanes.com/trust.
Install is one line, and your first report lands in ~2 minutes: Get started on backplanes.com.
Click here to join our Slack and say hello.
We hope you love Spotlight, and we can't wait to hear what it illuminates for you.