Docs menu

Agents and control

CLI in ChatGPT

Connect CLI to ChatGPT. What the connector can do, what it never takes or sends back, and the limits you set when you connect.

Explain it

You can run your apps on CLI by chatting with ChatGPT. Add CLI from ChatGPT's apps directory, sign in once, set your spending limits, and then ask in plain words.

How to do it: in ChatGPT, add the CLI app, sign in when it opens CLI in your browser, read what it can and can't do, and press Allow.

"Deploy github.com/me/my-app on CLI and tell me the address."

ChatGPT never sees your secrets or payment details, and every change it makes is recorded with its reason and an undo button.

The CLI connector lets ChatGPT deploy and run your apps, workers, databases, static sites and functions. It's hosted by CLI at https://api.clicloud.app/mcp/openai, so there's nothing to install.

Connect it

In ChatGPT, add CLI from the apps directory. If you're adding it by hand, use the URL https://api.clicloud.app/mcp/openai. ChatGPT opens CLI in your browser: sign in, read what it can and can't do, set your limits and press Allow.

The connector and Claude's connector (see /docs/claude) are separate. A sign-in made for one doesn't work for the other.

What it can do

It has a core set of about 40 tools:

  • See your projects, apps, deploys, logs, metrics and usage.
  • Create services from a GitHub repository or a public Docker image, deploy them, roll back, and add databases, domains and scheduled jobs.
  • Set non-secret variables, and references like ${{postgres.DATABASE_URL}}.
  • Run read-only SQL queries on your databases.

Tools that change something are marked that way, so ChatGPT asks you before each one. Tools that delete things or overwrite data are also marked as destructive, and tools that reach outside your account (like deploying from GitHub, or sending an email from your app) are marked as such.

What it never takes or sends back

  • Secrets. If ChatGPT tries to set a variable that looks like an API key, token, password or private key, CLI doesn't save it. ChatGPT gets a link to the service's Variables tab in the dashboard, and you paste the secret there yourself.
  • Credentials in answers. Database passwords, API keys and tokens are masked in everything CLI sends back. Copy them from the dashboard.
  • Payments. It can't add credit, withdraw, pay over x402, buy domains or sell APIs, and it never links to a payment. When a project runs out of credit, ChatGPT tells you the project needs more credit; its owner adds it in the CLI dashboard.
  • Who's on your team. It sees how many members a project has, not who they are, and it doesn't see the addresses changes came from.

It can't run commands either: no running commands inside your apps, no sandboxes, no creating, changing or running scheduled jobs, and no setting a service's start command. It can't give out agent keys. Those tools and settings aren't offered to ChatGPT; set them in the dashboard. It can list and delete scheduled jobs.

Limits you set when you connect

When you press Allow, you choose which projects it can use and the most it can spend a day ($10 unless you change it). Past that, CLI asks you to approve each request. Change the limits, or disconnect, under Account → Connected apps. Every change it makes is recorded in your project's activity as coming from the connector.

Sign-in and data

  • OAuth 2.1 with PKCE. If ChatGPT asks for the email scope, the approval screen says so, and then, if you sign in to CLI by email, ChatGPT can see that address. With a wallet, it sees only the address.
  • Access tokens last an hour and refresh tokens 30 days. CLI stores only hashes of them.
  • CLI gets only the arguments ChatGPT passes to a tool, never your conversation or files. What a tool returns (your projects, logs, deploy results) goes back to ChatGPT, with credentials masked.

Privacy: /privacy. Questions: [email protected].

Try it

Once CLI is connected, ask ChatGPT things like:

  1. "Deploy github.com/clicloud-app/starters (the nextjs-postgres folder) to a new CLI project called demo, with a Postgres database, and tell me the URL when it's live."
  2. "Show me my CLI projects, what each one cost this week, and anything that's failing."
  3. "My api service is returning 500s. Check its logs and recent deploys and roll back if the last deploy broke it."