Documentation
Workspace/Agent chat and visual editing•4 min read

Agent chat and visual editing

Send prompts, attach context, choose a model, dictate, and edit a preview visually.

Browse Docs

Agent chat and visual editing

Use chat to describe the outcome you want in your PHPSandbox project. The agent works with the active workspace and can inspect files, make changes, run commands and use connected tools when available.

Send a prompt

Enter your request and use Send. On desktop, Enter sends; a modifier shortcut is also available. On phones and coarse-pointer devices, Return inserts a new line so you can compose a longer request; use Send when ready.

A useful prompt names the desired result, who it is for and any constraints. Ask for one coherent change, review the result in Preview, and give the next instruction.

Attach context

Use the prompt input’s context menu to attach relevant files or other available project context. Attach screenshots or examples when they communicate the change more clearly than a description. Context belongs to the next request; check the attached chips before sending.

Do not paste passwords, API tokens or other secrets into chat. Use project secrets or your vault.

Choose a model

Open the brain icon beside the prompt to choose Standard or Advanced. Standard is the default. Advanced requires the project organization’s subscription entitlement; being a member of another paid organization does not grant access in the current one.

Each option describes its intended tasks and credit usage. There is no separate reasoning-level control.

Dictation

Use the microphone control to dictate a prompt and allow microphone access when asked. Insert the transcription into the draft to review it, or use the recording’s submit action to send it. Silent or empty recordings preserve the draft without sending a request. A microphone or transcription error is separate from an empty recording.

Visual editing

Open the running app in Preview and use the preview toolbar’s visual-edit control. Select the area you want changed, then describe the change. The selection gives the agent context; inspect the result after it makes the change.

Visual editing is useful for a visible area of an existing screen. For a new feature or a change across multiple screens, describe the work in ordinary chat instead.

Stop or continue work

Use Stop to interrupt an active run. Inspect any changes already made before asking the agent to continue. Starting a new conversation gives you a separate conversation history, not a separate project or automatic copy of its files.

Use Tasks when work should run in an isolated sandbox fork and be reviewed before merging.

Write a useful request

A clear request names what you want, who it is for, what success looks like and any important constraints. For example:

Improve onboarding for first-time restaurant owners. Remove jargon, make the
next action obvious and keep the existing billing flow. Prioritize mobile.

For a technical change, name the behavior that must remain stable, such as preserving the current API response while fixing validation. For visual feedback, say what should become clearer, easier to scan or less cluttered instead of asking only for something “better.”

Split unrelated features into separate requests. Review the first result before adding the next major requirement.

Match context to the problem

  • Use code selection for a specific block of code.
  • Add terminal output when a command or runtime error explains the failure.
  • Attach screenshots, diagrams, copy or API examples when showing the issue is clearer than describing it.
  • Use connected GitHub, Nightwatch or Sentry tools when the task needs evidence from those systems.

Check the context chips before sending. Large unrelated attachments make the task less clear; credentials belong in the secure secret or connection form.

Move around the workspace

Use Preview to inspect the running app and Code to inspect its files. Add Docs from the workbench view menu to read guidance without leaving the project. On mobile, use the workspace switcher to reach the workbench and return to chat. Project settings, opened with the sliders control, own project secrets, services and automation settings.

Keep Preview visible while refining a screen. After a visual edit, check that the intended area changed, nearby behavior still works and the result remains usable on a phone.

Continue, retry or start another conversation

Use Continue when offered to resume an interrupted conversation. Use Retry on a failed request when its original instruction is still correct; inspect the error and any changes already made first. Retrying does not imply that earlier actions were rolled back.

Keep the same conversation while working on one feature. Start another conversation for a different problem or a cleaner history. Start a new project when the codebase or foundation should change. A branch, a conversation and an isolated task fork solve different problems; use version control and Tasks for their respective workflows.