Skip to main content

​
The project workspace

Every project is split into two halves:
  • The conversation sidebar on the left
  • The code, preview, and backend area on the right
That setup is the main Rushed loop: ask, inspect, edit, preview, repeat.

​
Work with the chat like a project-aware assistant

Inside the conversation sidebar, Rushed can work against your actual files. Use the chat when you want to:
  • add or change multiple files
  • refactor with context
  • explain and then implement
  • update project structure, not just one line of code
Type @ in the prompt box to tag files directly.

​
Use the editor for direct control

The editor is best when you want to inspect or tweak code yourself. Helpful details:
  • file changes autosave
  • open tabs stay available across the session
  • binary files are detected and not shown as editable text
  • Cmd/Ctrl + K opens project search from inside the editor too

​
Highlight code to move faster

When you select code, Rushed gives you two high-value actions:

​
Add to Chat

Use this when you want Rushed to reason about a specific code block in context. It drops the selected code into the conversation so you can ask follow-up questions or request a broader change.

​
Quick Edit

Use this when the change is local and obvious. Shortcut:
  • Cmd/Ctrl + E
Quick Edit is ideal for:
  • renaming logic
  • tightening a component
  • changing copy
  • adding a loading state
  • patching a specific function
If your instruction includes URLs, Rushed can also pull in documentation context during the edit.

​
Preview is where you validate fast

Switch from Code to Preview to run the project inside the browser. Preview gives you:
  • a live app URL
  • restart controls
  • terminal output
  • custom install and dev commands
  • a direct open-in-new-tab path for the running preview

​
Backend is where you manage live app features

Switch to Backend when the project uses live data tools. Use it to:
  • open the embedded backend dashboard
  • confirm that auth or data wiring is connected
  • see setup issues that still need outside service keys
If the app only needs frontend code, you can ignore this tab.

​
When preview does not boot correctly

Open Preview settings and set:
  • Install Command
  • Start Command
This is especially useful after importing a repo with a non-standard setup. Good examples: 
Install Command: npm install
Start Command: npm run dev
For plain HTML projects, a good setup is: 
Install Command: npm install serve
Start Command: npx serve .

​
Best practice

Do not wait until the end to preview. Check often. Small preview loops catch weak layouts, broken flows, and dependency issues much earlier.