Skip to main content

Assistant workspace

The assistant workspace keeps project conversation and development controls in one screen.

Main areas​

AreaPurpose
SidebarSwitch sessions, open project gallery, account settings, and navigation.
Chat panelSend prompts, review assistant messages, and attach images.
ExplorerInspect files or switch to database tools.
Main panelToggle code and preview, publish, share, download, or open GitHub actions.
TerminalView output and runtime messages when terminal tools are available.
Cocoding AI assistant workspace with chat and editor panels
The workspace is built for repeated prompt, inspect, preview, and iterate cycles.

Inspect generated code​

Use Code when you need to understand what the assistant generated. You can open files from the explorer, review generated README files, inspect backend routes, and ask the assistant for changes.

Cocoding AI code view with generated project files
The code view shows the generated file tree, open files, and assistant progress in the same workspace.

Test the preview​

Use Preview after generation or after any major prompt. If the preview is unavailable, switch back to code and output to understand whether the app is still building or needs a fix.

Cocoding AI preview view
Preview is where you test the generated app before publishing or sharing it.

Common actions​

  • Ask the assistant to add screens, database fields, business rules, or UI refinements.
  • Switch to Code to inspect generated files.
  • Switch to Preview to test the running app.
  • Use the database explorer when the project needs persistent records.
  • Publish or share when the preview is ready.

Service and project controls​

The toolbar groups the service controls for the generated app:

  • Code / Preview switches between implementation and runtime testing.
  • Download exports the project when your plan allows downloads.
  • Share opens sharing controls for preview links.
  • Publish opens the hosted app when the preview is ready.
  • GitHub is where Git integration actions are exposed.
  • Project settings opens project-level options such as visibility and watermark controls.

Good workspace habits​

  • Make one change request at a time.
  • Mention the exact page or component that should change.
  • Confirm the preview after every major update.
  • Keep database changes explicit, especially field names and relationships.
  • When something fails, paste the exact output or preview error into the assistant and ask for a targeted fix.