News for hackers. Stuff that matters.

JXavierH

I know. Long live Gabe.
I'm all for decaf 100%.
That's why I moved to decaf. Love coffee, caffeine doesn't like me.
Implement bad idea, but use AI. That's the MO right now.
Re: on Thursday March 26, 2026 @03:32PM (#47534645)
Yes, I agree. I've been thinking about this problem within large orgs, code search, standards and how to surface them to developer agents. This looks quite promising.
Re:Artisanal software in the age of AI codegen on Thursday March 26, 2026 @03:28PM (#47534606)
I think there will always be people interested in the craft. Look at photography, there's loads of digital cameras that are technically better than any old 35mm film, but people still to that for the love of the craft.

Some developers will do the same. To each their own.

Vectimus does input inspection on approved MCP servers, but it can only catch known bad patterns too. It does not try to solve prompt injections or if a legitimate MCP server was comprimised and returned poisoned outputs. I do plan to add additional post took hooks in future that can scan the MCP server output too.

You're project is interesting. It's a bit of an MCP proxy in a way, moreso than Azure API Management, yours seems to give more functionality. I will definitely take a look.

Show HN: Vectimus – Cedar policy enforcement for AI coding agents

https://github.com/vectimus/vectimus

Hey HN. I built Vectimus because coding agents keep doing things they shouldn't and there's no runtime governance layer for the developer workstation.The problem: Claude Code, Cursor, Gemini CLI and GitHub Copilot let agents execute shell commands, write files and call MCP servers. Most developers disable the permission prompts because they slow you down. But that means the agent can rm -rf...

( Read More... | 2 comments | 2 points | on HN )