Skip to main content
neetoinvoice setup writes NeetoInvoice instructions into the config your coding assistant already reads, so the assistant knows the command surface without you pasting it in. Every target except claude writes into the current project directory, so run those commands from the root of the repository you want the assistant to use NeetoInvoice in. setup claude writes to ~/.config/neetoinvoice/claude-plugin and can be run from anywhere.
Re-run the setup command after every upgrade so the assistant learns any new commands. setup cursor and setup windsurf overwrite their rule file. setup copilot, setup gemini, and setup codex keep the rest of the file and replace only the section between the <!-- neetoinvoice:start --> and <!-- neetoinvoice:end --> markers, so re-running never duplicates it. setup claude removes and re-extracts the plugin directory.

Keeping an assistant current

The command catalog is the source of truth, and it always matches the installed binary:
Each entry has command, description, optional flags (with name, type, default, description, and required), and subcommands. Point an assistant at this whenever it asks about a flag or command that its instructions do not cover.

Cutting token use

Feed list and show output back to a model as TOON rather than JSON:
TOON carries the same data with keys and whitespace compressed. See Output formats.

MCP instead of the CLI

If you want an assistant to reach NeetoInvoice directly rather than by shelling out, connect it to the hosted MCP server instead. See Connect your AI assistant.