Editing your code

Every repository has one editable home. Keeping one source of truth prevents a browser edit, local commit, or GitHub change from silently replacing another version.

Last updated July 14, 2026

Edit pasted code in Tokay

Code submitted by paste or upload is managed by Tokay. Open the code's Source Code tab to edit files, add or remove files, or replace the full source.

Edits are saved as a draft until you choose Deploy Changes. The page shows when the draft differs from the running version. Before deployment, Tokay reviews the update again and flags issues such as a hardcoded credential or a missing value.

Edit git code in your local checkout

A Tokay hosted git repository is edited through git. Change the files locally, commit them, and run git push tokay. The dashboard shows the deployed source but does not offer browser editing.

For a GitHub connected repository, edit locally or on GitHub and push to the connected branch. GitHub is the source of truth, so the Tokay source view is also read only.

Move browser managed code to git as it grows

A small script can be easier to edit in the browser. When the project becomes part of regular development, switch it to git management from the code settings and clone it locally.

The switch is one way. Browser editing turns off after the repository moves to git so the two editing models cannot overwrite each other.

Bring useful context to an AI assistant

Copy for AI packages the source, runtime details, and current error output into one prompt. Apply the returned fix in the editable home of the code, then deploy through the normal review path.

Tokay may also propose a code change when a failure has a clear fix. The proposal appears as a diff and is applied only after approval. For git managed code, Tokay never writes the change back to the repository.

See Logs and debugging for the evidence included with a failure.