brichar01/hive.nvim

Code context, templated prompts and a coding agent, inside Neovim

---

💡 Mission statement

Hive implements a few core ideas:

• Separate suggestions from the code to reduce visual clutter in the IDE, but provide efficient tools for accepting suggestions, even partial suggestions.
• Control a task-oriented array of smaller agentic models and access patterns to them, hence the hive name, each insect does a single, specialised job, in parallel to others.
• Improve control and generation accuracy by allowing the user to fine tune the context sent to the models, while using enough generated context to give the model a good chance to produce the specific output the user wants (emphasising shape from automatically sourced code, direction from user input).
• Use local resources efficiently by giving the developer the tools and knowledge to produce good llm outputs, deferring to cloud solutions only when the task is appropriately large or general.

The aim of these core ideas is to provide a user with more control over code style than pure vibe coding. Allowing the user to inject their real world context into the code shape itself, providing effective abstractions instead of the common brute force and re-implementation methods typified by generated code.

🗺️ Status

Hive has three layers, each with its own command.

Agent (planned)

Neovim starts a Node service that wraps @earendil-works/pi-coding-agent. The service owns the agent loop. Neovim is the filesystem: the agent’s read, write and edit tools use buffers and never touch disk. An edit to an open file changes the buffer and leaves the file on disk as it was. A write to a new file opens a listed, modified, unsaved buffer. bash, grep, find and ls still read the filesystem.