MECHANISM

HOW CUE WORKS INSIDE YOUR BROWSER

You already know what you mean. Cue structures your natural intent into the exact format that LLM self-attention mechanisms reward—directly inside your active chatbox.

ROUGH INTENT0.0s

Type naturally

Type the way you think: fast, fragmented, and incomplete. Don't waste minutes crafting fake personas or verbose preamble.

“fix this sql query it takes 40s”
THE COMPILER0.4s

Cue structures it

Press Ctrl + Shift + Enter or tap the orb. Cue decomposes your draft into strict objective, schema, and boundaries.

[ROLE]: DBA Lead • EXPLAIN ANALYZE index inspection
TURN ONE OUTPUTTurn 1

Send it once

Your AI answers on turn one. No conversational rambling, no wandering hallucinations, and zero token-wasting back-and-forth loops.

✦ 1 roundtrip • 0 wasted tokens
ATTENTION DISCIPLINE

What Cue transforms behind the scenes.

Negative Boundary Constraints

Most hallucinations happen because prompts describe what to do, but leave what NOT to do wide open. Cue sets ironclad boundaries on verbosity, speculation, and ungrounded claims.

Local Tab Context Ingestion

Rather than copying code and terminal outputs repeatedly, Cue ingests preceding conversation artifacts and focuses the model's self-attention weights strictly on the relevant diff.

Structured Proofs & Verification

Requires concrete test vectors, boundary checks, or typed signatures so you can audit output correctness in seconds rather than reading 4 paragraphs of generic prose.

TRANSPORT LAYER

Bring Your Own Key (BYOK)

No middleman · Zero proxy servers

Your API keys are stored exclusively in your browser's sandboxed local storage (chrome.storage.local). When you trigger Cue, the compiler request dispatches straight from your browser engine to your provider API.

💻
Your Browser
Encrypted key storage
Cue
Local Cue Layer
Client-side structuring
🤖
Your Provider API
Direct token exchange
Ready to bring Cue into your browser?
CueGet Cue — Free→
KNOWLEDGE BASE

Fair questions. Direct answers.

No. Never. Cue is 100% client-side. The prompt structuring request is dispatched directly from your browser to your chosen AI provider (OpenAI, Anthropic, Gemini, OpenRouter, or local Ollama). There is no intermediary proxy server logging your text.