Set up
Runs on your computer. Pick your agent and operating system.
This project does not publish an install method we can turn into a config. Follow the README instead.
README
synced Oct 25, 2026Glossa
Codex ran out, and you're still working. Glossa lets you keep going on your computer with the ChatGPT usage still available through your subscription.
ChatGPT can use your existing checkout and development tools. Glossa is not another model or coding agent. See Why Glossa.
Quick start
Install the CLI with Node.js 22.9 or newer:
npm install --global @ariobarin/glossa
Install Glossa from the ChatGPT plugin directory. Without directory access, add https://mcp.glossa.sh/mcp as a custom OAuth MCP app.
Then open a terminal in the project and start Glossa:
glossa
The first time a computer runs Glossa, it shows a short pairing code. Enter it on the Glossa control panel from any browser to enroll the computer; a headless or SSH-only machine needs no local browser. The CLI stores only its revocable device credential, not a Google or Auth0 refresh token.
Follow the quickstart for the complete connection flow. Self-contained installers are covered in the operations guide.
Choose access
| Profile | Read files | Edit files inside the project | Run local commands |
|---|---|---|---|
read-only | Yes | No | No |
workspace (default) | Yes | Yes | No |
system | Yes | Yes | Yes |
The default allows guarded file edits without command execution.
systemis not sandboxed. Commands have the full environment, credentials, filesystem permissions, and network access of the operating-system account that started Glossa. They are not confined to the selected project.
Expose only a narrow project you trust. Keep credentials and regulated or otherwise sensitive data out of the workspace. See Security and permissions before enabling system.
How it works
ChatGPT
-> OAuth-protected Glossa relay
-> outbound worker running on your computer
-> one folder you selected
The worker initiates the connection, so Glossa does not require an inbound port. The relay routes authenticated requests to the active worker and does not store a repository copy.
Common controls
Press d in the worker terminal to list and revoke the account's devices, and q or Ctrl+C to disconnect the workspace immediately.
glossa unpair
glossa update --check
Security boundary
Structured file tools stay inside the selected root and reject absolute paths, parent traversal, and linked-path escapes. The relay and local worker both enforce the selected access profile. The system warning above describes the separate command boundary.
Read the public security overview, technical threat model, and private reporting policy for details.
Local development
Node.js 22.9 or newer and Docker are required:
npm run dev:setup
npm run dev
Stop local Postgres with npm run dev:down.
Local integration
The full flow (pairing, device management, MCP, and a live worker) runs locally against disposable Postgres, without touching the production tenant or relay:
npm run integration:local
See integration tests for what it covers.
For manual end-to-end work, run the development issuer and the relay in separate terminals:
npm run dev:auth # prints the relay .env and CLI environment values
npm run dev
Point the CLI at the local stack with the printed GLOSSA_RELAY_ORIGIN. The development issuer signs any requested identity and signs in to the control panel without a prompt, so redeem pairing codes there; never deploy it.