Files and logs

Last reviewed: September 27, 2026

Use these tools to inspect project details or diagnose an issue. Viewers can read; editing requires an appropriate role.

Open and edit a file

1
Open Files
From + choose Files, then select a file in the tree. Wait for it to load in the editor. Refresh the tree if a new file is missing.
2
Save a change
If editing is available, make the change and click Save. Wait for Saved; Unsaved means the change has not yet been stored.
3
Test or download a copy
Check Preview after saving. You can download a file or folder from its actions. If loading or saving fails, read the error and check your connection and role before retrying.

Task history: Codey requests, results, and usage. Open a task to review it.
Plan log: scope, questions, answers, and execution state. Return here to a deferred plan or stopped phase.
Log: build output or published-site runtime output according to its state.
Terminal: read-only development-server output. It is not a field for running typed commands.

1
Open the relevant log
Choose Log for a runtime issue or Terminal for the development preview. Wait for output after starting the relevant version.
2
Identify the failure
Tell Codey the message and the action preceding it without including secrets. If there is no output, check preview startup or deployment state.