Supported AI tools

Coming in the first release. This page describes behaviour being built for the first Gliss release. Details may change before it ships.

Gliss works with the AI tool you already use: Claude Code, Claude Desktop, Cursor and Codex, or any tool that reads AGENTS.md and speaks MCP.

Start with one sentence

Tell your AI:

Read https://docs.glissando.dev/for-ai-agents.md, then build me a Gliss app that <your idea>.

For AI agents is written for your AI. It checks the gliss client, signs you in, creates the app and builds it, and asks you when it needs you. The whole site is also available to AI tools as Markdown: add .md to any page’s address, or start from llms.txt at the root of this site.

The guidance in every app

Every Gliss app carries instructions for your AI, so it writes gliss.yaml correctly, keeps secrets out of the code and uses mock mode:

File	Read by
`AGENTS.md`	Codex, Cursor and most AI tools. The full guide; its text is on AGENTS.md
`CLAUDE.md`	Claude Code. A block Gliss manages imports `AGENTS.md`; the rest of the file is yours
`.cursor/rules/gliss.mdc`	Cursor
`.claude/skills/gliss-secrets/`, `.cursor/skills/gliss-secrets/`	Claude Code and Cursor: how to declare a secret without ever handling its value
`PROMPT.md`	You: a starter prompt with examples to paste into your AI

gliss init writes them into a new app. In any app’s folder:

Command	What it does
`gliss guide`	Print `AGENTS.md`
`gliss guide --check`	Say whether the files are missing or out of date
`gliss guide --write`	Write or refresh them. It replaces only files Gliss wrote, and only its own block in `CLAUDE.md`

Commit the files, so everyone working on the app gets the same guidance. Run gliss guide --write again after gliss update.

Connect the Gliss tools

gliss mcp gives your AI the Gliss tools: status, diagnosis and logs. It uses your gliss login session.

Claude Code
Cursor
Codex
Claude Desktop

claude mcp add gliss -- gliss mcp

In .cursor/mcp.json in the app’s folder, or ~/.cursor/mcp.json for every project:

{"mcpServers": {"gliss": {"command": "gliss", "args": ["mcp"]}}}

In ~/.codex/config.toml:

[mcp_servers.gliss]
command = "gliss"
args = ["mcp"]

In Settings, Developer, Edit Config, add to claude_desktop_config.json:

{"mcpServers": {"gliss": {"command": "gliss", "args": ["mcp"]}}}

If Claude Desktop cannot find gliss, give its full path as command: command -v gliss prints it on macOS and Linux, where.exe gliss on Windows.

Letting your AI release

By default your AI can read status, diagnoses and logs, but not change anything. To let it release from your machine too, start the server with --allow-release (Beta and your Preview) or --allow-release=preview (your Preview only), and --dir for the app’s folder. It then asks you before every release. This builds with Docker on your machine, so it needs what gliss release needs. Soon most people won’t need it: each push to your work branch will build your Preview.

Never allowlist or auto-approve gliss_release. Each call replaces what runs at a stage.

Get started

Build apps

Administer

Engineers

Troubleshooting

Supported AI tools

Start with one sentence

The guidance in every app

Connect the Gliss tools

Letting your AI release

​Start with one sentence

​The guidance in every app

​Connect the Gliss tools

​Letting your AI release

Start with one sentence

The guidance in every app

Connect the Gliss tools

Letting your AI release