Skip to content
View diablo-noir999's full-sized avatar

Block or report diablo-noir999

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
diablo-noir999/README.md

👋 Hi, I'm Noir

Typing SVG

I'm Noir. Most of my time goes into the scaffolding around coding agents: memory stores, safety hooks, skill packs, editor extensions, the occasional protocol bridge. The models improve every month. The plumbing that keeps them useful and careful mostly doesn't exist yet, so I write it.

Concretely, that's an 18-skill megaplugin for MiMoCode sitting on top of a persistent memory engine (SQLite in WAL mode, hybrid FTS5/BM25 plus TF-IDF search, optional embeddings from a small local ONNX model), a fork of OpenCode called flakecode where those ideas live closer to the core, and Zed extensions for languages other editors forgot. Java and C still show up whenever a mod API or a grammar needs finishing. Rust when I want the compiler to argue with me first.

"I trust agents more since I started giving them less room to improvise."

🔌 agent plumbing  ·  🧠 memory engines  ·  🌑 compiling in the dark


🧠 Currently Thinking About

  • Whether persistent memory actually makes an agent better or just louder. Mine can recall a decision from three weeks ago; whether it should bring that up unprompted is a separate question I haven't settled.
  • Where guardrails belong when an agent can touch real files: the prompt, the protocol, or the hook that fires before the damage. Leaning toward the last one lately.
  • DSLs nobody respects. ZenScript got a finished grammar partly out of spite, and now every half-done tree-sitter grammar I walk past looks like unfinished homework.

🗡 Things I've Wired

Project What it does Stack
mimocode-powerpack Megaplugin for MiMoCode: persistent memory with hybrid search, knowledge graph, context analytics, safety and notify hooks, 18 skills, 7 specialized subagents TypeScript, SQLite
flakecode OpenCode fork that pulls frequently-used MiMoCode features into the core, with the powerpack plugin ported along TypeScript
zenscript-toolkit Zed extension unifying ZenScript highlighting, Minecraft .lang files, and a bundled LSP for bracket-handler completions Rust, Tree-sitter
tree-sitter-zenscript Completed ZenScript grammar for tree-sitter; picked up another fork's stubs and finished class declarations, expressions, statements, and types C

⛏ Earlier Work

The Minecraft MCP bridges that started all this are quieter these days, but they still stand: jei-mcp indexes 21K+ items and about 27 million recipe relations offline in SQLite with FTS5, graph traversal included, and bq-mcp writes BetterQuesting quest data behind dry-run defaults, backups, and an audit log. Letting a model loose on a questbook taught me some lessons the loud way, and the hooks in everything above carry those scars.


🛠 Stack & Tools

Rust Java TypeScript JavaScript Python C Kotlin

MCP HuggingFace

Node.js Bun SQLite

Git Linux Bash GitHub Actions VS Code Zed


🔍 Elsewhere in My Forks

Not everything worth reading lives in the table above. There's a mappings-heavy minecraft-modding-mcp server for digging through decompiled source, a Gemini-behind-Claude-Code proxy in gemini-for-claude-code, and a Fossify Gallery fork, which mostly means I use the app daily and like having the source around.


💼 Open for Collaboration

Interesting problems welcome, especially the ones where somebody warns me "this probably isn't possible." Agent tooling, editor extensions, language servers, mod integrations, cursed save formats, all fair game. If your project deserves a bridge, open an issue on any repo above. I read everything, even when replies take a week.

Status Let's Build


Contact Me

GitHub

@diablo-noir999's activity is private