Skip to main content
Use the CLI with an AI coding assistant to manage NeetoEngage in plain language. The neetoengage setup commands add NeetoEngage instructions for your assistant, while --toon keeps command output compact for it to read.

​
Set up your assistant

Run the subcommand for the tool you use: Every subcommand except setup claude writes into the current directory, so run it from the root of the project the assistant works in. The copilot, gemini, and codex commands place their section between <!-- neetoengage:start --> and <!-- neetoengage:end --> markers and replace that section on re-run instead of adding a duplicate. Re-run the command after every CLI upgrade so the instructions match the installed version.
setup claude prints two slash commands to finish the installation inside Claude Code:
After setup, your assistant can check the commands and flags available in your installed CLI version:
The command prints the complete catalog as JSON.

​
What the assistant can do

Once set up, ask in plain language, for example “a customer asked for CSV export of the roadmap, file it”. The instructions tell the assistant to search for a duplicate first, add the customer as a voter on a match or create a new request otherwise, and keep customer details in the private note. See Filing a customer’s request.

​
Tips for agent workflows

Prefer --toon when the assistant needs to read a list or record, and --quiet when it needs to pipe an identifier into the next command. See Output formats.
  • Authenticate once with neetoengage login; the assistant reuses the stored credentials.
  • When several workspaces are signed in, the assistant must pass --subdomain <name> on each command.
  • Run neetoengage doctor first to confirm the assistant is authenticated and connected.