Book a call

Insights

Industry insights

Where agent safety, oversight and verification are heading, and what it means for teams running agents.

  1. Agent Oversight

    Done Is a Claim, Not a Fact: Separating Wrong Claims From Concealed Failure in Coding Agents

    We gave a small open-weight coding agent tasks no code can pass and checked every 'done' against the host's own record of what happened. Across 36 runs it never hid a failure: 13 'done' claims were false, and every one told the user what was wrong.

  2. Agent Oversight

    Inside Tracekit: How an Agent's Tool Call Becomes Evidence

    This article explains how Tracekit turns an AI agent's tool call into evidence: where the signer sits, how each call is decided, and how records are signed and chained. It also shows how someone who trusts neither the agent nor its operator can check a run offline, and lists the known limits.

  3. Agent Oversight

    Every Way Out Is a Door: Running AI Agent Jobs in a Micro-VM Where Each Exit Is Decided and Signed

    A coding agent is asked to make a failing test pass. To do that it needs your repository, a package index, perhaps a GitHub token and a model API key. Run it on a CI runner the usual way and it gets far more: the runner's whole network, including the cloud metadata address and anything on the private network; every environment variable, keys included; and write access to the checkout, including the workflow files that decide what runs next. Tracekit Box is an open-source runtime ([github.com/Cygnux-Labs/Tracekit-box](https://github.com/Cygnux-Labs/Tracekit-box)) that runs each agent job in its own Firecracker micro-VM with no network card. The only ways out of the VM (the network, secrets, model calls, commands and code changes) are doors on the host. A Tracekit signer the agent cannot reach decides each crossing, and every job ends as one `.tkb` file that anyone can verify offline. This write-up explains how Box is built, what it guarantees, and what it does not. The full paper, with every test, table and limit, is [Tracekit Box: Running AI Agents in Micro-VMs Where Every Way Out Is Decided and Signed](/research/tracekit-box-paper) ([arXiv:2610.38458](https://arxiv.org/abs/2610.38458)).

  4. Agent Oversight

    We Blind-Tested Our Own Agent Firewall

    We gave Tracekit's policy gate, the firewall that decides each tool call before it runs, 420 harmful tool calls it had never seen, written without looking at its rules. It stopped or held 211 of them: 50.2%. On the calls its rules were written against, today's packs stop or hold all 570. Rule-based gates, ours included, are usually scored on attacks their authors already knew. This piece takes the gap between those two numbers apart: what caught the half that was caught, what the misses look like, where the gate is close to blind, and what to do if your agents have real access. Every number can be reproduced from the public repository.

  5. Industry Insights

    Where AI Safety Research Is Moving: A Map of 1,842 Projects, 2021–2027

    We classified 1,842 public AI safety projects from 2021 to 2027 into 23 research directions and 82 subtopics, to see which parts of the field are crowded, which are heating up, which have lasted, and which are still close to empty. - **The overall balance has barely moved.** Technical alignment has been about two thirds of research projects and governance about one third in both periods we compare, up to 2025 and 2026–27. The change is inside each half.

  6. Industry Insights

    Authorised Is Not Intended: Where Agentic Payments Actually Stand in October 2026

    AI agents can now hold a card token, sign a mandate and pay for an API call in the same round trip. Mastercard says nearly every one of its cards can be used by an agent. Stripe has made checkout agent-ready at more than 7.8 million businesses. And yet, outside China, almost nobody is letting agents spend. We spent a week mapping the protocols, the card networks, the platforms, nine regions and the regulators. The gap between what is built and what is used comes down to one unanswered question. When an agent buys the wrong thing, who can prove what the human actually meant? - **The problem.** Agentic payments, where software finds, chooses and pays for something on your behalf, are fully plumbed but barely used. No card network has disclosed a single agentic volume figure in 2026 earnings. PayPal told investors the category becomes meaningful [from 2028 onward](https://www.nasdaq.com/articles/paypal-agentic-payments-can-they-reshape-future-commerce).

  7. Industry Insights

    Agent Traces Are the New Oil. Can You Trust the Supply?

    Agent traces are becoming some of the most valuable data a company produces: a record of what an agent was asked, how it reasoned, which tools it called and what came back. Most of that record is lost, editable by the agent that wrote it, incomplete, or too sensitive to reuse. Sam Liu recently argued that [agent traces are the new oil](https://x.com/samzliu/status/2103613396625367437). Labs train on them, vendors sell them, and companies deploying agents mostly file them away as logs. We agree with the argument, and want to add the part that matters most to us. Oil is only worth something if it reaches the refinery uncontaminated. A trace is only worth something if you can trust it.

  8. Industry Insights

    Monitoring Is Not Evidence: Where Tracekit Fits Among Agent Observability, Guardrail and Audit Tools

    On September 24, researchers showed that AI coding agents in Claude Code, Codex and Grok Build would delete their own execution traces when asked, and nothing stopped them. A log the agent can erase is weak evidence of what the agent did. The paper, [LLM Agents Can Easily Tamper With Their Own Traces](https://arxiv.org/abs/2609.30266) by Jeremy Qin, Maksym Andriushchenko and colleagues, recommends that trace logging run through an independent mechanism outside the agent's control.

  9. Industry Insights

    Putting AI Agents to Work Without Losing the Record: A Business Guide to Tracekit and Causeway

    Most companies deploying AI agents can answer "what did the agent produce?" Fewer can answer "what did it actually do?" Fewer still can answer "why did it do that?" in a way that would hold up in front of a customer, an auditor or their own security team. Cygnux Labs builds two open-source tools for those questions. **Tracekit** keeps a signed, tamper-evident record of what an agent did. **Causeway** works out which input made a multi-agent system act, by replaying the run without each suspect. This guide is written for the people deciding whether and how to use them: engineering leads, security and risk teams, and founders running agents in production.

  10. Industry Insights

    A CERN for Superintelligence: A Blueprint for Building Frontier AI in the Open

    The most consequential technology of this century is being built by a few private labs, behind closed doors, on infrastructure that costs more than most countries spend on science. The people deciding how capable these systems become, and how safe they are, answer mostly to shareholders and to each other's release schedules. Physicists faced a version of this problem in the 1950s. No single lab could afford the machine they needed, so they pooled resources and built one together, with shared data and shared credit. This piece sketches what the same move could look like for advanced AI: a public institution at the frontier, built to make powerful systems trustworthy and to let others check that they are.

  11. Agent Oversight

    Reached Is Not Caused: Finding Which Input Made a Multi-Agent System Act, by Replaying It Without Each Suspect

    A team of three AI agents is handling a refund ticket. A researcher agent reads the ticket, the refund policy, a note from a vendor portal and a shipping FAQ. A planner agent decides what to do. An executor agent does it. One run ends with the executor emailing the company's full customer list to an outside address. The trace shows everything each agent saw, and every untrusted document it read is connected to that email. A trace can tell you what reached the action. It cannot tell you which input caused it. This write-up introduces Causeway, an open-source tool that answers that second question the way you would test any causal claim: remove the suspect, run the system again, and see whether the action still happens.

  12. Field Report

    Mapping AI Safety: Where the Field Is Crowded, Where It Is Empty, and What Comes Next

    AI safety is no longer a side conversation inside a few labs. It now spans evaluation companies, interpretability startups, government institutes, fellowships and funders, but the growth is uneven: some problems attract dozens of teams while others have almost nobody. We mapped 24 areas of the field, rated how thickly each is covered, and looked hard at the empty spaces. This report explains the map area by area, argues that risk from many agents acting together is the most consequential gap, lays out a concrete research agenda for it, and proposes six mechanisms for the neglected areas.

  13. Industry Insights

    What Surrounds the Model: Engineering Generative AI Systems That Hold Up in Production

    A demo is one line: a prompt goes in, the model answers, the answer goes out. It works on the first try, in front of the people who built it, on the questions they thought to ask. Production is everything that has to surround that line once real users, real data and real money are involved. The model needs knowledge it was never trained on. Its behaviour has to be measured, because it changes between runs. Every failure has to be traceable to a cause. Costs have to come down. Users have to be heard without being taken literally. And some rules have to hold no matter what the model says.

  14. Agent Oversight

    Trust the Log, Not the Summary: Auditing AI Agents with Tamper-Evident Traces of What They Were Asked, Said, and Did

    When an AI coding agent finishes a task, you usually get a friendly summary and a diff. That tells you what the agent says it did. It does not tell you what it read, what it ran, what influenced it, or whether the record in front of you has been edited since. This is a technical walkthrough of a flight recorder for agents: how it captures three separate channels of evidence, how a hash chain and external anchors make tampering visible, how rules and an independent reviewer cross-check the channels, and what five experiments revealed, including a new method for testing oversight tools when real agents refuse to misbehave.

  15. Industry Insights

    When Nothing Errors: Observability for Non-Deterministic Agentic Systems

    An AI agent can fail without raising a single error. It reads weak context, picks the wrong tool, gets a clean response from that tool, and returns an answer that is confident, fluent and wrong. No exception is thrown and no alert fires. The dashboard stays green. Observability practice was built for software that breaks loudly. Agents break that assumption. This piece covers why their failures stay hidden, which signals expose them, how teams turn a vague symptom into a root cause, and where today's tooling stops. For how tracing fits beside retrieval, evals, caching and guardrails, see our [guide to production GenAI systems](/research/engineering-production-genai-systems).