Glossa

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

Add this MCP server to ChatGPT using OAuth:

https://mcp.glossa.sh/mcp

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

The default is useful for most code changes because it permits guarded file edits without command execution.

system is 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

CLI distributable builds pin React to production mode so idle HUD refreshes do not accumulate development timing records in memory.

Stop local Postgres with npm run dev:down.

Local integration

The full flow — pairing, device management, MCP, and a live worker — runs locally without touching the production tenant or relay:

npm run integration:smoke

The harness starts a local development issuer, boots the relay against local Postgres, pairs a throwaway device, and round-trips an MCP read_file through a live worker before revoking the device.

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 environment values. The development issuer signs any requested identity and auto-approves pairing; never deploy it.

User documentation

• Quickstart
• Why Glossa
• Security and permissions
• Support
• Privacy
• Terms

Technical documentation

• Operations guide
• Architecture
• Protocol
• Security and threat model
• Self-hosting

Maintainer and review documentation

• Managed identity and reviewer access
• MCP metadata operations
• Restricted Data review
• Submission readiness
• Plugin submission demo recording
• App submission packet