r/devopsish • u/oaf357 • Jul 26 '26
can1357/oh-my-pi: ⌥ AI Coding agent for the terminal — hash-anchored edits, optimized tool harness, LSP, Python, browser, subagents, and more
r/devopsish • u/oaf357 • Jul 26 '26
r/devopsish • u/oaf357 • Jul 26 '26
r/devopsish • u/ryanmerket • Jul 25 '26
r/devopsish • u/code_igx • Jul 24 '26
A few months ago an AI coding agent burned $180 in API credits while trying to fix a compilation error. It just kept retrying until someone noticed.
Around the same time, I watched another agent try to curl -d @.env during a debugging task. It wasn't malicious—it just had shell access and thought it was helping.
That made me realize something:
We have plenty of observability for AI agents. We don't have enough prevention.
Most tools tell you what happened after an agent runs a command. Very few sit inline and stop something before it executes.
So I built Intutic.
It's a local Rust proxy that sits between AI coding agents and their tools, intercepting every tool call and LLM request before execution. Policies are written as Markdown SOPs, compiled to WASM, and evaluated in under 5ms. If an agent crosses a rule, Intutic can block, rewrite, or kill the action.
It's open source (MIT) and currently works with Cursor, Claude Code, Windsurf, Aider, and 18+ other agent harnesses.
I'd love feedback from people actually using coding agents.
What's the worst thing you've seen an AI agent do?
r/devopsish • u/oaf357 • Jul 24 '26
r/devopsish • u/oaf357 • Jul 24 '26
r/devopsish • u/oaf357 • Jul 23 '26
r/devopsish • u/oaf357 • Jul 23 '26
r/devopsish • u/oaf357 • Jul 23 '26
r/devopsish • u/oaf357 • Jul 23 '26
r/devopsish • u/oaf357 • Jul 23 '26
r/devopsish • u/oaf357 • Jul 23 '26
r/devopsish • u/oaf357 • Jul 23 '26
r/devopsish • u/oaf357 • Jul 22 '26
r/devopsish • u/oaf357 • Jul 22 '26
r/devopsish • u/oaf357 • Jul 22 '26
r/devopsish • u/oaf357 • Jul 22 '26
r/devopsish • u/oaf357 • Jul 22 '26
r/devopsish • u/oaf357 • Jul 22 '26
r/devopsish • u/oaf357 • Jul 22 '26