The AI Assistant Built Into Your Editor
All posts
Guide#AICoding

The AI Assistant Built Into Your Editor

Cloudpen Team

Cloudpen Team

October 16, 2026·3 min read

Switching between your editor and a separate AI chat means copying code out, copying answers back, and losing context each time. Quill removes that step. It lives inside the Cloudpen editor and already knows your active file, your selection and your project structure.

What Quill can do

  • Explain code: select any block and ask for a plain-language explanation
  • Find bugs: scan a file or selection for logic errors
  • Suggest fixes: when a problem is found, Quill proposes a concrete fix and explains it
  • Generate code: ask for a function, a component or a scaffolded feature
  • Refactor: get advice on structure, naming and efficiency

Because Quill reads your open project before it answers, you do not need to paste context into a chat box.

Usage on Cloudpen's shared pool

By default Quill runs on Cloudpen's shared AI pool, with daily limits by plan:

PlanRequests per dayMax characters per request
Free102,000
Pro10020,000
Team1,000100,000
Enterprise5,000Unlimited

Bring your own key (Pro and above)

If you already have API access to an AI provider, or you simply need more requests, connect your own key. While it is active, Quill uses it exclusively and Cloudpen's daily limits no longer apply. Your usage is governed by your provider's quota and billing.

Supported options include OpenAI, Anthropic, Google Gemini, Groq, xAI, OpenRouter, and any provider with an OpenAI-compatible endpoint through a custom base URL. For OpenRouter you can search the live model catalog right from the key form.

How to connect a key

  1. Open Settings → Quill AI
  2. Choose your provider
  3. Paste your key and pick a model (add a base URL for custom providers)
  4. Click Save, then Use this key
  5. Open any project and use Quill as usual

You can save several keys from different providers and switch the active one at any time. Removing the active key sends Quill straight back to the shared pool.

Your key stays protected

Keys are encrypted with AES-256 the moment you save them. Only the last few characters are ever displayed, and all requests are proxied through our backend, so your raw key never reaches the browser. If your key returns an error, Quill shows a clear message with a link back to Settings, and it does not silently fall back to the shared pool, so you always know which account is being used.

Images too

With your own key, Quill can also read images. Drop a screenshot, an error dialog or a design mockup into the chat and it reasons over the image alongside your code.

Try Quill on your next bug and see how much context-switching disappears.