Create and automate · 4 min read

Work with Vibe Code

Vibe Code works on source files in a folder you choose. It can propose and save edits, but it does not run your code or tests. You remain responsible for reviewing and verifying the changes.

Connect your code folder

  1. Choose Vibe Code

    Select Vibe Code in the desktop mode row, or open Add files & more and choose it from the mode selector. If the mode is unavailable, it may not be enabled in your environment.

  2. Open a local folder

    Choose the smallest relevant project folder and grant access in the browser picker. Direct editing requires a browser that supports folder read/write access; uploading a file does not grant access to its original.

  3. Set the scope

    Use Files & context to preview and select files, or type @ to pin references. Only use selected files restricts access; an empty selection in that scope allows no file access. Pins alone do not restrict the scope.

Ask for a focused change

Describe the desired behavior, the files involved and how you will verify the result. Use Add files & more for available reasoning and Skills settings. Expand the progress row to inspect what was searched, read or changed.

Vibe Code is an editing mode. For a strictly read-only task, choose Local workspace and keep its Read-only setting instead.

Example: “Update the empty-state text in the settings screen. Preserve its layout and accessible labels, and show me the proposed changes.”

Review before saving

Inspect each proposed file change before approving it. Automatic edits require an explicit choice for the current session; do not enable them unless you accept that proposed changes may be saved without individual review.

After saving, run your own tests and inspect the result in your development tools. A successful save means the file was written, not that the program works.

Stop, undo and reconnect safely

Stop cancels pending work but does not undo files already saved. Check the change list before retrying. Originals are backed up in .studio-recovery before saving, and Undo is available for eligible changes in the current session.

Avoid editing the same files in another application during a task. If a file changed or a save is uncertain, inspect the current file and recovery information before trying again.

Saved local history stays on this device. Reopening may require folder permission again; edit approval and Undo are not restored. Disconnecting does not remove files or their recovery backups.

Privacy and supported files

Local previews stay on your device. Submitted tasks send relevant file paths and text to cloud AI, so select only material you are allowed to share. Hidden and protected paths are excluded, but secrets inside ordinary source files can still be sent; inspect your scope.

This mode is for supported plain-text source files, not binary assets or office documents. Large folders and files are bounded, and partial reads are possible. If a needed file is missing, narrow the folder or selection and check the message shown in the app.

Didn’t solve the problem?

Contact support and include the feature, model, and steps that led to the issue.