flash_us0101

4 ms·

1. 1.▲
   by flash_us0101 6mo ago

   How is it different from Context Hub https://github.com/andrewyng/context-hub ?
2. 2.▲
   by flash_us0101 7mo ago

   CLI is great when you know what command to run. MCP is great when the agent decides what to run - it discovers tools without you scripting the interaction. The real problem isn't MCP vs CLI, it's that MCP originally loaded every t
3. 3.▲
   by flash_us0101 7mo ago

   That's close to what I'm thinking about. Curious what debugger setup you're using with agents - are you giving them access via MCP or just having them run CLI commands?
4. 4.▲
   by flash_us0101 7mo ago

   Timestamps aren't the issue. The problem is the cycle itself: stop the process, add the log line, restart, wait for the right conditions to hit that code path again. For anything timing-sensitive or dependent on external state, each re
5. 5.▲
   by flash_us0101 7mo ago

   Most replies here are about writing code faster. But there's a gap nobody's talking about: AI agents are completely blind to running systems. When you hit a runtime bug, the agent's only tool is "let me add a print state
6. 6.▲
   by flash_us0101 7mo ago

   Thanks for sharing! Was thinking of doing similar tool myself. That's great alternative to -dangerously-skip-permissions
7. 7.▲
   Show HN: Detrix – Give your AI agent a live debugger for running processes(github.com)

   1 points by flash_us0101 7mo ago|0 comments