// the take
A personal monorepo of MoonBit CLIs and libraries by nikiv — things like a menu-bar launcher (comet), fish-shell helpers (fishx/fishy), a Zed opener, and notably a full coding-agent framework (lib/flow) with SDKs for Java, Node, and Python. It's for people curious about MoonBit as a real-world, multi-package language in practice, or MoonBit devs who want to borrow one of these tools wholesale.
lib/flow is a genuinely substantial coding-agent implementation — tool calling (read_file, execute_command, search_files, todo tracking), job management, model loading, and three language SDKs — worth studying even outside MoonBit. Several packages carry real test files (agent_test.mbt, pruner_test.mbt, loader_test.mbt, tool_test.mbt) rather than being untested scripts. It's one of the larger public MoonBit codebases, useful as a reference for structuring multi-package MoonBit projects with moon.pkg.json. CI workflows exist for the flow component against multiple MoonBit toolchain versions.
Everything is built and deployed through the author's own unreleased 'flow' CLI (f setup, f deploy-<cli>) rather than plain `moon build`, so there's no standard entry point for an outside user to pick up one tool without adopting that whole toolchain. No LICENSE file is visible at the repo root, which leaves the legal status of reusing any of this code genuinely unclear. The repo mixes unrelated personal utilities (shell aliases, a keymap tool, a Zed launcher) with a serious agent framework, so there's no coherent single product to depend on — you take the whole grab-bag or none of it. Contributing guidance ('use AI, all meaningful PRs merged') suggests a low review bar, which matters if you're trusting this for anything beyond personal tooling. MoonBit itself is still a young language with a small ecosystem, so hiring, tooling, and long-term support risk sit on top of whatever's built here.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →