Troubleshooting

Normal access expiration should refresh and retry once; it should not log out the desktop account. If Session expired repeats, check connectivity, reopen the app, and sign in once if prompted.

Record the time, model, task ID if visible, and whether the account menu still shows the user. Provider authentication failures should appear as service errors, not user logout.

Gyroscape requires a valid terminal stream event before accepting completion. Abrupt closure is retried or reported incomplete, and partial tool arguments are not executed.

Inspect Changes before retrying so you know what state continues.

Check whether the command waits for input, produces output, or runs in the background. Send input only when you understand the prompt. Stop or interrupt when it should not continue.

Development servers are intentionally long-running and belong in a background terminal.

Confirm the project and workspace, folder existence, and operating-system access. Then inspect Git status or Changes.

A diagnosis-only task can correctly make no edits. Ask to implement when you want files changed.

Bring Gyroscape forward and review the pending card. Approve, reject, or request a narrower action. Auto-approve does not dismiss hard consent.

Keep the task intact and collect app version, operating system, failure time, project type, visible error, and smallest reproduction. Redact secrets and private source from diagnostics.