WeSearch
What we have learned at OpenShell applying formal methods to control AI agents

What we have learned at OpenShell applying formal methods to control AI agents

Alex Watson· ·13 min read · 0 reactions · 0 comments · 8 views
More from OpenShell Research ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

OpenShell researchers are applying formal methods to address the security challenges of managing large-scale AI agent systems. They utilize the Z3 library to create formal proofs that ensure agent policy changes remain within approved boundaries. This approach aims to prevent agents from bypassing sandbox restrictions through complex combinations of available tools and credentials.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,996 of its stories.

Original article
OpenShell Research · Alex Watson
Read full at OpenShell Research →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherOpenShell Research
Canonical URLhttps://nvidia.github.io/OpenShell-Research/dev-notes/posts/2026-09-10-learning-formal-methods-agent-policy-prover/
Publication timeTue, 15 Sep 2026 14:40:05 +0000
Retrieval time2026-09-15T14:46:52.519Z
Last seen2026-09-15T14:46:52.519Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterQUEj5T5-NkOr · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

What we have learned applying formal methods to control AI agents An intro to using formal methods to reason about permission changes in long-running AI agents. Dev Note September 10, 2026 OpenShell Alex Watson OpenShell Team @ NVIDIA In this post- we’ll dive into how permission review breaks at agent scale, and how to use the Z3 open source library to write a formal proof that a policy change proposed by an agent stays inside what you approved. Why permission review breaks at agent scale AI agents are becoming smarter, and the work we ask them to do is becoming increasingly autonomous. Today, many of us use small groups of agents to iterate on code one PR at a time with Claude or Codex.

Excerpt limited to ~120 words for fair-use compliance. The full article is at OpenShell Research.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from OpenShell Research