Ano

For developers

Ano is built to be driven from the terminal as much as from the chat window. There is a real CLI, real Claude Code skills, and a plugin surface so your agents, tools, and workflows can live in the same room your team is already in. Open source where it matters. Plain Node and npm where it counts.

github.com/ano-chat/ano-cli MIT github.com/ano-chat/ano-skills Open

The CLI

@ano-chat/cli is the official command line interface for Ano. Read messages, send replies, search workspace context, stream live events. Every command can return structured JSON, so any agent can drive it without scraping output. 

# install (Node 18+)
npm install -g @ano-chat/cli

# sign in (or pass --key for non-interactive use)
ano auth login

Source: github.com/ano-chat/ano-cli  ·  Package: npmjs.com/package/@ano-chat/cli

Claude Code skills

@ano-chat/skills teaches Claude Code how to work with Ano: drive the CLI, read workspace context, send messages, and parse the <ano_payload> blocks that the desktop app sends to your shell when you forward a message or thread. Two skills for now, more on the way. 

# install the skill plugin into Claude Code
claude plugin install @ano-chat/skills

Source: github.com/ano-chat/ano-skills

Highlights

A few of the things the CLI lets your terminal and your agents do today.

  1. 01 Read a channel from the terminal
    ano messages read --channel general
ano messages read --channel general --json
  2. 02 Send a message or a DM
    ano messages send "Deploy is live" --channel engineering
ano dm send "Can you review this?" --to "Jane"
  3. 03 Search across the workspace
    ano messages search "staging error"
ano messages search "staging error" --json
  4. 04 Wire Claude Code to Ano
    # one command. no config file to babysit.
ano setup claude
  5. 05 Stream live events for an always-on agent
    ano connect

    Returns a long-lived stream of workspace events: new messages, replies, edits, presence. Wire it into any process that knows how to read stdin.

Get involved

Open issues and PRs against either repo. We read every one. For early access to the plugin API, deeper integration questions, or just to say hello, reach .