Quick Start Guide
This guide will walk you through creating your account, setting up your first project, and using Polaris’s AI features.This quickstart is for users of the hosted Polaris service. If you’re self-hosting, see the Installation Guide.
Prerequisites
All you need is:- A modern web browser (Chrome, Firefox, Safari, or Edge)
- A GitHub account (for authentication)
- 5 minutes of your time
Step 1: Create Your Account
Sign Up with GitHub
Navigate to the Polaris homepage and click “Sign in with GitHub”. Polaris uses Clerk for secure authentication with GitHub OAuth.
Authorize Access
Grant Polaris permission to access your GitHub profile. This enables future features like repository import/export.
Step 2: Create Your First Project
Open Project Dialog
Click the “New Project” button in the dashboard. You’ll see a prompt input powered by AI.
Projects in Polaris are stored in Convex with this schema:
Describe Your Project
Type what you want to build in natural language:
- “Build a todo app with React”
- “Create a landing page for a SaaS product”
- “Set up a Node.js Express API”
Step 3: Create Your First File
Open File Explorer
In the center panel, you’ll see your project’s file tree. Right-click in the explorer to see options.
Create a New File
Right-click and select “New File” or click the + icon. Name your file with an extension (e.g.,
app.js, index.html, README.md).Polaris supports syntax highlighting for:
- JavaScript/TypeScript (
.js,.ts,.jsx,.tsx) - HTML (
.html) - CSS (
.css) - JSON (
.json) - Markdown (
.md) - Python (
.py)
Step 4: Use AI Suggestions
Polaris provides real-time code completions as you type.Start Coding
Begin typing in your file. After a brief pause (300ms debounce), Polaris analyzes your code:
Review Suggestions
You’ll see ghost text (grayed out) suggesting your next code. This appears inline at your cursor position.
Step 5: Use Quick Edit (Cmd+K)
Quick Edit lets you modify code using natural language instructions.Select Code
Highlight the code you want to modify. A tooltip will appear with two options:
- Add to Chat: Adds the selection to your conversation
- Quick Edit (⌘K): Opens the inline edit interface
Describe the Change
Press Cmd+K (Mac) or Ctrl+K (Windows/Linux). Type your instruction:
- “Add error handling”
- “Convert this to async/await”
- “Add TypeScript types”
- “Refactor using modern ES6 syntax”
Step 6: Chat with AI Assistant
The conversation sidebar provides a ChatGPT-like interface with full project awareness.Open Conversation Panel
The left sidebar shows your conversation history. Each project has its own conversation thread stored in Convex:
Ask Questions
Type questions or requests in the input at the bottom:
- “Explain how this function works”
- “Add a README with installation instructions”
- “Find bugs in my authentication logic”
- “Suggest improvements to this component”
Next Steps
You’re now ready to build with Polaris! Here are some things to try:Organize Files
Create folders, rename files, and structure your project
Explore Keyboard Shortcuts
Use Cmd+K for quick edit and Tab for suggestions
Try Different Languages
Create Python, TypeScript, or Markdown files
Use Documentation URLs
Include URLs in Quick Edit to teach AI about libraries
Tips for Success
Make suggestions more accurate: Type at least 2-3 lines before expecting suggestions. The AI needs context to understand your intent.
Write better prompts: Be specific in your Quick Edit instructions. Instead of “improve this”, try “add input validation and error handling”.
Leverage conversation memory: The AI remembers your full conversation. Reference previous messages with “like you suggested before”.
Troubleshooting
Suggestions aren't appearing
Suggestions aren't appearing
- Wait 300ms after typing for the debounce delay
- Ensure you have at least 2-3 lines of code for context
- Check that your cursor is at the end of a line
Quick Edit (Cmd+K) isn't working
Quick Edit (Cmd+K) isn't working
- Make sure you’ve selected code first
- Try clicking the “Quick Edit” button in the tooltip instead
- Check browser console for errors (F12)
Files aren't saving
Files aren't saving
- Files auto-save after 500ms of inactivity
- Check your network connection
- Look for the save indicator in the tab
AI responses are slow
AI responses are slow
- Claude Sonnet 4 can take 2-5 seconds for complex requests
- Try shorter, more focused prompts
- Consider using Gemini 2.0 Flash for faster responses (see Installation)