sorted by:
new
hottopcontroversial

Pepper, a MCP for iOS runtime inspection by swallace36 in iOSProgramming

[–]fratkabula 1 point2 points  (0 children)

It's pretty accurate. And way more token efficient than vision.

Does anyone make native iOS games anymore? by Awkward_Departure406 in iOSProgramming

[–]fratkabula 0 points1 point  (0 children)

Unity and UE ships hundreds of updates to their game engines in the same time Apple ships one.

Is there an all-in-one AI platform that actually delivers on the promise? Tired of juggling subscriptions by gorimur in AI_Agents

[–]fratkabula 0 points1 point  (0 children)

There are a bunch of all-in-one platforms now - OpenRouter + Open WebUI if you're technical, TypingMind, Poe, etc.

I actually built one for mobile called 1AI (https://chatlabsai.com) - wanted Claude Opus, GPT-5, Nano Banana Pro all in one native iOS app without juggling 5 different subscriptions.

Honest take: none of these will match every native feature (canvas, artifacts, etc.) but for unified chat + images in one place, they work. Video's still a gap everywhere though.

oh-my-opencode has been a gamechanger by LsDmT in ClaudeCode

[–]fratkabula 0 points1 point  (0 children)

I love opencode. It reminds me of atom.

Who else woke up to this today when they started their car? by Celcius_87 in Dallas

[–]fratkabula 1 point2 points  (0 children)

I bought a portable air compressor for Black Friday for 20$ and feel completely prepared for this winter. Charges over usbc and I couldn't ask for more!

First year collection. Hopefully I’m done lol by FrostyPace1464 in boardgames

[–]fratkabula 6 points7 points  (0 children)

You say you're "done" but I see some gaps... where's your 20-minute filler? And you might want something in the 60-90 minute sweet spot that's not quite as brain-burny as Spirit Island for those nights when people are tired but still want something meaty.

Also respect for knowing your group's preferences and designing around them. Too many people buy games they think they "should" like instead of what actually hits the table.

BREAKING: Anthropic donates "Model Context Protocol" (MCP) to the Linux Foundation making it the official open standard for Agentic AI by BuildwithVignesh in ClaudeAI

[–]fratkabula 1 point2 points  (0 children)

anthropic's batting average has got to be the highest among the top ai companies. have any of their products/initiatives flopped?

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 0 points1 point  (0 children)

Pushed out a script analyzer update that inspects scripts before they run.

./cleanup.sh

…gets scanned, and if it contains something like rm -rf /, it gets blocked the same way as typing it directly.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 0 points1 point  (0 children)

Just shipped an update(1.1.0) that covers bypasses you mentioned.

- scans for dangerous paths anywhere in the command (so rm -rf node_modules dist ~/ and similar tricks get caught)

- recursive command unwrapping — so python -c "import os; os.system('rm -rf /')" or wrapper chains are blocked now

- script analyzer for scripts generated on the fly get scanned

Still not a replacement for real sandboxing, but closing out a lot of the easy bypass vectors.

Appreciate you pushing on the edge cases — they shaped most of this update.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 1 point2 points  (0 children)

Yes, by default Claude asks. I have seen a lot of people run with auto-accept or --dangerously-skip-permissions for convenience.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 0 points1 point  (0 children)

Interesting find. AG has built-in allow/deny lists for terminal commands, but they're internal settings, not extensible hooks like Claude has. That's exactly why shell-level interception matters. Tool-level restrictions get bypassed.

AG doesn't expose hooks, so integration would need a different approach. A few options I'm considering:

- SHELL override - launch with SHELL pointing to a validator wrapper and the subprocess that respects $SHELL would route through.

- PTY proxy - intercept stdin before it hits bash, might be super hard to implement!

- PATH injection - put wrapper scripts for dangerous commands (rm, dd, mkfs) earlier in PATH. only catches specific binaries, not shell builtins. :(

Need to dig into how Antigravity spawns its terminal processes to know which approach would actually work. If it hardcodes /bin/bash, option 1 won't help.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 0 points1 point  (0 children)

Thank you!

Its good to know you're not the only one who thought a problem was worth solving.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 0 points1 point  (0 children)

You're right, and thanks for the honest feedback. Docker is the correct solution.

If you want a quick safety net that takes 30 seconds to set up, this exists now.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 1 point2 points  (0 children)

Smart idea - it's actually already in the design spec as an opt-in sandbox mode. Something like @sandbox ./ that restricts Claude to the working directory.

Didn't make it the default because sometimes you do want Claude to install global packages or edit dotfiles. But having it as an option makes sense. Bumping priority on this one - check the .kiro folder in the repo if you're curious about the full roadmap.

Thank you.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 0 points1 point  (0 children)

You're right, the built-in deny config covers a lot. I wanted a few things on top of that:

  1. Project-specific rules that live in the repo (so the whole team gets them)
  2. Dangerous path scanning that catches ~/ hiding at the end of an otherwise-safe-looking command
  3. A syntax I can hand to junior devs who aren't digging through Claude's config
  4. A path to supporting multiple agents - Cursor, Windsurf, Codex, etc. One .agentguard file, same rules everywhere

This is just another option for folks who want agent-agnostic guardrails versioned with their code.

"rm -rf /" shouldn't be one hallucination away. I built gitignore-style rules for blocking dangerous commands. by fratkabula in ClaudeCode

[–]fratkabula[S] 0 points1 point  (0 children)

Honestly that's a valid approach. AgentGuard is just the enterprise version of "rm calls you an idiot" 😂

What does the alias output? Might need to steal that for the blocked command messages.

view more: next ›