Code run lifecycle

yCode works on explicitly selected repositories in isolated runs. Supported web, desktop, editor and command-line surfaces share scoped identity and review requirements.

A prompt alone does not grant permission to push, merge, delete or read unrelated paths. If authentication fails in a desktop client, check the browser callback and client session.

Work is the execution inbox for tasks that are waiting, running, need attention, completed or failed. It helps distinguish an active run from a finished result.

A completed run still needs output review. An approval should identify the action, target and effect; reject an unexpected or overly broad request.