Imagine if AI found the answer while you wrote the question. Now imagine you could do that anywhere. Welcome to OpenCues.
OpenCues brings AI wherever you type. Just type _ and AI will fill in the blank. Anywhere.
OpenCues brings AI wherever you type. Just type _ and AI will fill in the blank. Anywhere.
npm install -g opencues, then opencues install <host>. Full instructions on the OpenCues repo. Or ask AI to read it for you.
Just type _ and AI will fill in the blank. If you don’t like what AI did, Ctrl+Alt+←/→ to select the changed text, then Ctrl+Alt+↑/↓ cycles through other things it could have said, or right back to exactly what you typed. Your original text is always one cycle away.
Yes, OpenCues is fully open source. The source code is public on GitHub under the Apache-2.0 License, meaning anyone can use, modify, or contribute to its development. We are trying to grow a community that files issues, submits pull requests, and extends functionality.
To explore and advance the frontier of human to AI interfaces.
Yes. Bring an API key from Cerebras, Groq, OpenAI, Anthropic, Gemini or OpenRouter, connect through your existing Claude or OpenAI subscription, or run local models via Ollama.
No. OpenCues works with what you already have: an existing API key, or an AI subscription you already pay for.
You can use OpenCues almost anywhere in Chrome, Claude Code, OpenCode, Gemini CLI, and in your terminal via the standalone oc-shell app. Full guide: AI in any text field.
OpenCues itself is free and open source. It plugs into whatever AI service you choose, so the only cost is your model usage with that provider (several, like Cerebras, have free tiers).
OpenCues has no servers and collects nothing. Your text goes directly from your machine to the model provider you configured, on your own key or subscription. Config lives in local files, and the optional identity feature keeps personal values on your machine by default.