My Claude code refused to publish my article three times because it thought I was stealing my own work Alignment is fragile when models are the only place decisions get made

🌈 Prismor: open source runtime control plane for AI agents New this week: 1. The mirror: Prismor runs your agent's tools itself, checking every call and masking secrets in the output 2. Blocks show up live inside Claude Code, right under the prompt 3. 5 more agents governed: Cursor, Grok, OpenCode, OpenClaw, Hermes Agent 4. Ask for access straight from a block with prismor egress request 5. Subagents governed in the open 6. Bypasses from a live attack test, closed OSS: github.com/PrismorSec/prismo…

🌈 Prismor: open source runtime control plane for AI agents New this week: 1. One Extensions tab for everything your agents used: skills, MCP servers, secrets, packages, plugins, hooks, each with its usage history 2. Top network calls: every host your agents reached, with what was blocked 3. The session page explains a run: first failure, retry loops, a diff of what changed. Locate jumps to the failed call 4. Share a session like a doc, with teammates or anyone with the link, and find one by describing it 5. Native Google Antigravity hooks, and ElevenLabs voice agents governed through the LLM proxy 6. Shell rules see past quote tricks and egress blocks tell s human how to unblock in agent OSS: github.com/PrismorSec/prismo…

obsidian-wiki just crossed 3.5k stars on GitHub Your agent forgets every past session. This gives it a simple yet effective memory engine: - turns docs, PDFs and past agent chats into linked notes in your Obsidian vault - answers with [[wikilink]] citations to its sources - works in Claude Code, Codex, Cursor, Gemini CLI and more - Chrome extension: save pages as you browse and fill forms from your vault (it never submits) - 4.4x faster answers, 83% correct vs 44% on the same model and vault - open source, MIT pip install obsidian-wiki github.com/Ar9av/obsidian-wi…

🌈 Prismor: open source runtime control plane for AI agents New this week: 1) Rules know who is asking: A rule can check the tool's arguments, its target and the end user's roles: block refunds over 500 unless the user is in finance, Users are verified against your identity provider (any OIDC), not taken on the caller's word 2) The MCP gateway only lists the tools a user can actually use, and refreshes the list when the user changes 3) Policy tests: Write the expected outcome per user, run them in CI with a GitHub Action, and the console runs them before every publish 4) Speaks AuthZEN, the OpenID authorization standard, so gateways and apps that use it can ask Prismor for a decision directly 5) The LLM judge re-checks a sample of allowed calls after the fact, to catch what the rules let through 6) Every event records the policy version that decided it. "Why?" explains a flagged event against that version, and flagged events land in a review queue 📷 github.com/PrismorSec/prismo…

Claude auto just killed our startup, because the auto-mode now asks users before deleting anything? It's great anthropic is focusing on model alignment, but we are building something bigger Harness alignment agonstic of agent and LLM We ran various dangerous commands and prompt injections against vanilla claude code and then with Prismor and the harm rate dropped from 68% to 0% there are lot of other unsolved business specific cases where users would like to control their fleet of agents on: •⁠ ⁠egress rules •⁠ ⁠supply chain package rules •⁠ ⁠secret redaction •⁠ ⁠custom policies which is why we are building Prismor, completely open source and independent of models github.com/PrismorSec/prismo…

I recently had a on why would anyone even build in open source if they're putting cutting edge novelty and research out for free? And we get this question by VCs a lot agent safety should be accessible to all because if agents can act, people should be able to control it in the first place That's our mission at Prismor

🌈 Prismor: open source runtime control plane for AI agents. New this week: 1. Agent-to-agent traffic is governed. A2A messages go through the same proxy endpoint and the same policy as tool calls, and a message can be blocked before the receiving agent reads it 2. Managed model endpoints. Point Bedrock, Vertex or Azure traffic at prismor proxy. SigV4 signing and OAuth are handled for you 3. Policy explains itself. Every rule shows which layer defined it and why it blocks or only warns 4. Extension ledger. Every skill, plugin, hook and MCP server your agents load, where it came from, what it caused, and which sessions ran under it 5. Proxied calls now count toward per-session cost on every provider, streaming included 6. Additions to dashboard : hook timing on every call and Prometheus panels built from real session date 📷 github.com/PrismorSec/prismo…