I kept hitting model failures on phones that I couldn't reproduce in the office. LangFuse didn't catch it. LangSmith didn't catch it. So I built the thing I wanted: a flight recorder for AI running on real devices.
heavybit.com/library/article…
@irangareddy
Hey — saw your post about the agent wiping the DB / running destructive commands
We’ve built Rykan V specifically for this: policy guardrails that block dangerous shell/file actions before they execute.
You can also run ryk scan to see every dangerous command your agent has run in past sessions.
Open-source here if you want to try or star it: github.com/christopherkarani…
When you run an agent through ryk, we try to put a real OS filesystem boundary around it — Seatbelt on macOS, Landlock on Linux.
Not PATH tricks. Kernel rules on the child process.
A short walk through how that works.
Before you trust a policy, dry-run the scary string: ryk explain "rm -rf /" | ryk test "rm -rf /" --format json. Same decision path the live session uses.
Don't assume ryk start left you protected. ryk doctor diagnoses policy, hosts, packs, sandbox backend features, and network policy status. Try: ryk doctor | ryk doctor -v
“it’s really not close” what a load of bs, the model good, Its on par with 5.5 better at following instructions and the honest factor is really underrated. doesn’t write overly defensive code, so less slop. you have a skill issue my friend
Your Swift AI agents just went multiplatform 🚀 SwiftAgents adds Linux support → deploy Agents- to production servers Built on Swift 6.2, running anywhere ⭐️ github.com/christopherkarani…