Hacker News

Show HN: Codeman – a blunt launcher forcing you to pick a Codex permission level

Hacker News - Fri, 02/13/2026 - 12:11am

I kept getting burned by “what permissions am I running with?” so I built Codeman: a thin launcher around codex that forces an explicit security level each run (read-only, orkspace-write, networked, full), with a clear confirmation panel before higher-risk modes. It also supports resuming by session UUID and optional Slack/Discord webhook notifications. Repo: https://github.com/shabo/codeman Feedback welcome: naming, UX, and whether the level breakdown matches how you actually work with Codex.

Comments URL: https://news.ycombinator.com/item?id=46999161

Points: 1

# Comments: 0

Categories: Hacker News

Show HN: Roe.md generate your own OpenClaw-like bot from a single Markdown file

Hacker News - Thu, 02/12/2026 - 11:43pm

Hi fellow HNers,

I am guld and I created ROE.md (https://github.com/guld/ROE.md), a proof of concept single Markdown file that let's you raise your own custom personal OpenClaw-like AI assistant from scratch.

With a very stripped-down feature-set of course. (For now. Still alpha)

All you need is a little vibe code magic from your favorite AI coding tool. Select your favorite programming language (yes really) and hope that it has been grokked by the SOTA models. (I am looking at you Ruby programmers).

I came up with the idea last week when I first heard of the OpenClaw craze. Listening to steipete's wild stories I was wondering... if the agent can create all these skills by itself... what if we spin it further and let the agent create itself from a single Markdown file. This should work!

How to use it?

Your coding agent of choice should load the ROE.md markdown file, you answer a few questions and it builds a minimal OpenClaw-like personal assistant for you. It comes with a single build in tool (execute_bash).

This is dangerous I know, but it works.

Anyways... I tested it with OpenCode and the Kimi-2.5 model and Python selected. (OpenCode is great!) With a few questions answered and some bugs fixed the custom agent works nicely in CLI mode with a locally running gpt-oss-20b through LM Studio.

How did I create the ROE.md file?

Mostly by hand, with a very high level overview of the architecture, almost no architecture at all. I rather focused more on adding a lot of example call-responses and used first person singular to improve prompting (Thanks to a comment thread on here where postalcoder verified that first person makes the difference with Gemini)

The next few days I want to extend the ROE.md file to contain more succinct API examples to make sure it works with more languages.

- TODOs alot... Fix, Test, Repeat

Challenges:

- Getting more programming languages to work in as few prompts as possible with the big local models such as Kimi-2.5. Tested Bash, Python, Go, Ruby, and a few others but Python works best.

- Not getting to specific in pseudocode.

- Keeping its structure general enough to be applicable to most programming languages.

- Making it work with weaker local models.

For more details check out the mini-tutorial in the README (https://github.com/guld/ROE.md).

This project and the power of vibe coding brought back the enjoyment I felt when I started out writing my first line of code on an "empty piece of Windows Editor paper" more than two decades ago.

What do you think? Is vibe coding crazy cool or is it just me?

Comments URL: https://news.ycombinator.com/item?id=46999010

Points: 1

# Comments: 0

Categories: Hacker News

Yori – Isolating AI Logic into "Semantic Containers" (Docker for Code)

Hacker News - Thu, 02/12/2026 - 11:17pm

Hi HN, I've been a developer for some time now, and like many of you, I've been frustrated by the "All-or-Nothing" problem with AI coding tools.

You ask an AI to fix a bug or implement a function, and it rewrites the whole file. It changes your imports, renames your variables, or deletes comments it deems unnecessary. It’s like giving a junior developer (like me) root access to your production server just to change a config file.

So, 29 days ago, I started building Yori to solve the trust problem.

The Concept: Semantic Containers Yori introduces a syntax that acts like a firewall for AI. You define a $${ ... }$$ block inside a text file.

Outside the block (The Host): Your manual code, architecture, and structure. The AI cannot touch this. Inside the block (The Container): You write natural language intent. The AI can only generate code here.

Example: myutils.md

```cpp EXPORT: "myfile.cpp"

// My manual architecture - AI cannot change this #include "utils.h"

void process_data() { // Container: The AI is sandboxed here, but inherits the rest of the file as context $${ Sort the incoming data vector using quicksort. Filter out negative numbers. Print the result. }$$ } EXPORT: END ``` How it works: Yori is a C++ wrapper that parses these files. Whatever is within the EXPORT block and outside the containers ($${ }$$) will be copied as it is. When you run `yori myutils.md -make -series`, it sends the prompts to a local (Ollama) or cloud LLM, generates the syntax, fills the blocks, and compiles the result using your native toolchain (GCC/Clang/Python).

If compilation fails, it feeds the error back to the LLM in a retry loop (self-healing).

Why I think this matters:

1. Safety: You stop giving AI "root access" to your files.

2. Intent as Source: The prompt stays in the file. If you want to port your logic from C++ to Rust, you keep the prompts and just change the compile target.

3. Incremental Builds (to be added soon): Named containers allow for caching. If the prompt hasn't changed, you don't pay for an API call.

It’s open source (MIT), C++17, and works locally.

I’d love feedback on the "Semantic Container" concept. Is this the abstraction layer we've been missing for AI coding? Let me hear your ideas. Also, if you can't run yori.exe tell what went wrong and we see how to fix it. I opened a github issue on this. I am also working in making documentation for the project (github wiki). So expect that soon.

GitHub: https://github.com/alonsovm44/yori

Thanks!

Comments URL: https://news.ycombinator.com/item?id=46998870

Points: 1

# Comments: 0

Categories: Hacker News

Pages