v_CodeSentinal

4 ms·

1.
by v_CodeSentinal 7mo ago
Nothing super fancy. For me “proof” just means the agent has to make its intent explicit in a way I can check before running it. For example: 1) If it wants to delete a file, it has to output the exact path it thinks it’s deleting. I normal
2.
Show HN: Autonoma – Python secret fixer that refuses unsafe fixes(github.com)
2 points by v_CodeSentinal 7mo ago|0 comments
3.
by v_CodeSentinal 7mo ago
The deny list section hit home. I keep seeing agents use unlink instead of rm, or spawn a python subprocess to delete files. Every new rule just taught the agent a new workaround. Ended up flipping the model — instead of blocking bad action
4.
Why we stopped allowing autonomous fixes in production (even when tests pass)?
1 points by v_CodeSentinal 8mo ago|1 comments
5.
by v_CodeSentinal 8mo ago
Hi HN — I’m the creator of Autonoma. Autonoma is an open-source, local-first autonomous code remediation engine. It analyzes code at the AST level and uses a local LLM (currently Qwen 2.5-Coder) to automatically detect and fix a bounded set
6.
Show HN: Autonoma – a local-first autonomous code remediation engine(github.com)
1 points by v_CodeSentinal 8mo ago|1 comments
7.
by v_CodeSentinal 8mo ago
Hard agree. As LLMs drive the cost of writing code toward zero, the volume of code we produce is going to explode. But the cost of complexity doesn't go down—it actually might go up because we're generating code faster than we can
8.
by v_CodeSentinal 8mo ago
The point about 'no such thing as a free lunch with processes' is something I wish more junior EMs understood. I've seen so many teams treat process as a pure 'fix', ignoring that it's always a trade-off: you a
9.
by v_CodeSentinal 8mo ago
This is the classic 'plausible hallucination' problem. In my own testing with coding agents, we see this constantly—LLMs will invent a method that sounds correct but doesn't exist in the library. The only fix is tight verific
10.
by v_CodeSentinal 8mo ago
I've been working on this problem specifically in the context of autonomous coding agents, and you hit the nail on the head with 'implicit context'. The biggest issue isn't just that documentation gets outdated; it'
11.
by v_CodeSentinal 9mo ago
I built Autonoma because I was tired of Copilot suggesting code that didn't compile. Autonoma is a local daemon that acts as an "L5 Autonomous Engineer". It doesn't just autocomplete; it autonomously fixes bugs, security
12.
Show HN: Autonoma – Air-Gapped AI Code Engineer (L5 Autonomy)(vihaaninnovations.github.io)
1 points by v_CodeSentinal 9mo ago|1 comments
13.
by v_CodeSentinal 9mo ago
The 'scaling with intelligence' argument often ignores the 'scaling of verification costs'. As models get smarter and cheaper, the cost of generating complex code or artifacts approaches zero. However, the cost of ver
14.
by v_CodeSentinal 9mo ago
The biggest challenge I've seen with these 'infinite narration' layers on top of simulation games is context context window management. As a RimWorld colony grows, the state data (pawns, inventory, health, history) explodes e
15.
by v_CodeSentinal 9mo ago
This is a fascinating pattern—treating 'agent skills' as composable dependencies rather than monolithic prompts. I'm curious about the execution model: How are you handling the security implications of an agent pulling and ex
16.
by v_CodeSentinal 9mo ago
Interesting approach. How does this architecture handle the 'lost in the middle' phenomenon when the retrieval volume increases? I've found that simply increasing volume often degrades reasoning quality unless re-ranking is e
17.
by v_CodeSentinal 9mo ago
This is a useful collection. As someone building local agents, I find the biggest bottleneck isn't 'discovering' skills, but defining the permission boundaries for them. Does this directory categorize skills by their 'sa