Starting pay as you go no longer sends you to a separate checkout page: an embedded Stripe Checkout form mounts right on the billing page. Security and IT admins get a clearer picture too, with device coverage that reports whether a device is actually enforcing the policy Speakeasy served it, and a security audit log that's now separate from configuration changes. More on this in Billing and Device Agent.

Features

• Start pay as you go from an embedded checkout — Start pay as you go without leaving the billing page: the checkout endpoint returns the client secret and publishable key an embedded Stripe Checkout form mounts with. (#8284, @alx-xo)
• Device agents report the policy they actually enforce — Each device now reports the policy version it applies, every tool's enforcement outcome, its agent version, and its update posture; Speakeasy stores the latest report per user per machine so a device's attested state can be checked against what was served to it. (#8116, @bradcypert)
• Device coverage shows whether policy is actually enforced — Every active device now carries a policy state of attested, outdated, unreported, or halted, coverage counts break down by those states, and you can filter managed devices by them. A fresh report also counts as liveness, so a halted device that stopped polling still shows as active instead of dropping out of coverage. (#8117, @bradcypert)
• Security activity gets its own audit log — The audit log shows configuration changes by default and switches to security activity, such as an agent's runtime admitting its own workload identity, with consecutive entries from the same agent grouped by day. (#8238, @aa-wong)
• The agent install command sets up OpenClaw too — The same one-line install now adds the agent gateway, installs the observability plugin with the agent's own key, and turns on conversation access, so connecting an agent to OpenClaw no longer needs separate manual steps. (#8108, @speakeasyforgebot)
• GitHub Actions is coming as a workload platform (rolling out to select organizations) — A guided setup lets a job in one repository sign in as an agent with its own GitHub token, through the Speakeasy device agent action, so CI jobs can call MCP servers and send hook events without a stored secret. It's listed under Coming soon for most organizations until a stable speakeasyd release supports it, and reaches organizations with the workload-platform-github-actions flag on first. (#8273, #8418, @subomi)

Bug fixes

• Slack webhook handshakes can no longer be forged into events — Slack trigger webhooks now treat the URL verification handshake as challenge-only: a request that skips signature verification as a handshake can never be ingested as a real event. (#7854, @speakeasyforgebot)
• Kit assistants on managed GKE respond again — The server now finds a Kit sandbox's pod through its assigned Sandbox when the cluster doesn't label pods with their claim, instead of waiting out the turn and retrying on a fresh runtime. (#8425, @danielkov)
• Kit assistants on managed GKE start again — Their sandbox containers now request enough memory to pass the cluster's admission policy, and a Kit resource budget that would be rejected now fails at startup instead of at first use. (#8421, @danielkov)
• Agent setup codes stay valid until they expire — An agent's one-line setup command can now be run more than once, up to 15 minutes after it's generated, instead of being spent by the first fetch. (#8278, @mfbx9da4)
• The agent install script only asks to store the key when needed — It now prints the note to store SPEAKEASY_AGENT_KEY only when it configured a client, such as Claude Code or Codex, that reads the key from the environment; an OpenClaw-only install skips it. (#8348, @mfbx9da4)
• OpenClaw CLI commands no longer hang after installing the plugin — The observability plugin's hooks process now starts on the first hook instead of when OpenClaw loads it, so openclaw plugins install and other CLI commands no longer stall. (#8347, @mfbx9da4)
• The install hooks self-test no longer leaves a fake session — The agent install script's hooks self-test no longer leaves an empty "New Chat" session and a tool call under every new agent. (#8349, @mfbx9da4)
• OpenClaw's Codex-harness turns capture the user's prompt — Turns that run on OpenClaw's Codex app-server harness now report the prompt that started them, which that harness doesn't otherwise fire an event for. (#8092, @mfbx9da4)
• New agent identities can send hook events right away — When its creator holds hook-ingestion permission, a new agent identity now gets it too, scoped to its project, instead of needing an admin to grant it separately afterward. (#8073, @speakeasyforgebot)