Skip to main content
The Notis CLI gives your coding agents one path to your Notis integrations. Instead of reconnecting Gmail, Slack, GitHub, Notion, Linear, Calendar, and MCP servers separately for every agent, sign in to Notis once and let the agent work through Notis. The Notis desktop app keeps your CLI session tied to your Notis login. It also syncs the built-in notis-cli skill to your local agents, so Codex, Claude Code, and Cursor know how to run the Notis CLI through NPX without separate setup.

​
Why this helps

  • One connection flow — Connect integrations in Notis, then use them from any supported local agent.
  • Less expired-auth cleanup — The Notis desktop app keeps the CLI session tied to your Notis login.
  • One command style — Your agent does not need to remember different setup commands for Codex, Claude Code, Cursor, or other agents.
  • More than 1,000 integrations — Agents can reach the integrations available through Notis without separate MCP setup in each agent.

​
Get set up

Install and sign in to the Notis desktop app. It keeps the Notis CLI authenticated and syncs the Notis agent skills locally. To check that everything is ready, run: 
npx --package @notis_ai/cli@latest -- notis doctor
If the check fails, open the Notis desktop app and sign in again.

​
Use it with an agent

First, connect the integrations you want in Notis. Then ask your coding agent to use the Notis CLI whenever it needs one of them. For example: 
Use the Notis CLI to find my latest GitHub issues and draft a Slack update.
The agent can look up the right integration action and run it through your Notis account. You do not need to configure Gmail, Slack, GitHub, Notion, Linear, or Calendar again inside each agent.

​
Connect a new integration

If an integration is not connected yet, the CLI returns a Notis link. Open it, complete the connection, and ask the agent to retry. You can also connect and manage integrations from the Notis portal at Settings → Integrations. See Integrations for the full help-center guide, including multiple accounts and labels. Once connected, that integration becomes available through the same Notis path.

​
Install any CLI on your Cloud Computer

You don’t need a local machine to use a command-line tool with your agent. Ask Notis to install any CLI — Datafast, Stripe, Supabase, PostHog, Vercel, GitHub (gh), psql, aws, gcloud, and many others — on your Cloud Computer and run it there. 
Check the Datafast CLI for what's our best performing country in the last week in terms of number of trials.

Use the Stripe CLI to pull last month's payouts and break them down by country.

Use the Supabase CLI to count signups grouped by plan over the last 30 days.
CLIs you install on the Cloud Computer are persisted per user — once a CLI is installed and signed in, it stays available across every future conversation, channel, and skill run on your account. You don’t reinstall it the next time you ask. If the CLI needs to sign in (for example with an API key or OAuth flow), Notis will ask you for the credentials it needs — or use the matching Notis integration when one is already connected.
CLIs installed in the Cloud Computer sandbox are separate from the Notis CLI your local coding agent runs through NPX. They run inside the sandbox and are used by Notis on your behalf there. If you need another CLI to be callable from your local coding agent’s shell, install it locally as you normally would.