AI assistants

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. Run the command from the repository you are working in.

neetoinvoice setup claude

neetoinvoice setup cursor

neetoinvoice setup windsurf

neetoinvoice setup copilot

neetoinvoice setup gemini

neetoinvoice setup codex

Command	What it writes
`setup claude`	Registers the NeetoInvoice plugin with Claude Code, including `plugin.json`, hooks, and the CLI’s skill file.
`setup cursor`	`.cursor/rules/neetoinvoice.mdc`
`setup windsurf`	`.windsurf/rules/neetoinvoice.md`
`setup copilot`	Appends to `.github/copilot-instructions.md`
`setup gemini`	Appends to `GEMINI.md`
`setup codex`	Appends to `AGENTS.md`

Re-running a setup command refreshes its block in place rather than duplicating it, and content outside the block is preserved.

Keeping an assistant current

The command catalog is the source of truth, and it always matches the installed binary:

neetoinvoice commands

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:

neetoinvoice time-entries list \
  --client 7c1f5e2a9b \
  --project 89d1b47d9f36af3c9ecf \
  --toon

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.

Getting Started

Commands

Keeping an assistant current

Cutting token use

MCP instead of the CLI

​Keeping an assistant current

​Cutting token use

​MCP instead of the CLI

Keeping an assistant current

Cutting token use

MCP instead of the CLI