Checks and project readiness

Run a read-only readiness check

Open Checks, choose the approved project and select Check workflow. You can run this local inspection before connecting ChatGPT.

The check inspects whether the project can support the development sequence. It does not create test files, execute project code, stage files or make a commit.

Read the result

• Ready: the project’s inspection, safe editing, sandbox verification and Git workflow capabilities are available.
• Limited: inspection works, while one or more later steps need setup or are intentionally unavailable.
• Blocked: RepoTunnel cannot safely validate the approved workspace.

Follow the recommended next step

Read each reported item and the Recommended next step rather than relying only on the overall badge. A read-only project, disabled commands, unavailable native sandbox, missing discovered preset or unsupported Git layout can limit the workflow.

Fix the specific setup or permission issue locally and select Run again. Keep read-only access when the requested work is inspection; a Limited result can accurately describe that intentional choice.

Verify the remote path separately

Checks shows whether the gateway/client path is connected alongside project readiness. A successful local check does not establish that a remote AI client has authenticated and can call the tools.

Use Connect to configure the transport, then verify a real workspace-list or bounded-read request from the client.

Move through the development loop

Once the required capabilities are ready, inspect the project, prepare the intended change, run an appropriate verification command and inspect Git state.

Use Commands for actual build/test/check execution. Return to History for recorded results and file recovery, and to Git when you are ready to review or stage the intended changes.