Troubleshooting

A file tAI is looking for doesn't seem to be there

Check whether it was actually included in the clone. Very large files and repos over the file-count cap leave some files out of the local copy.

1. Ask tAI to fetch that specific file with github_read_file.
2. If it's a symbol or keyword rather than a known path, ask it to use github_search_code instead, which reaches the whole repo on GitHub.

Reconnecting GitHub

If tAI says GitHub is not connected, or access stops working mid-conversation, most often the cause is that access was revoked from GitHub's side rather than from tAI. To reconnect:

1. Open Settings → Connectors.
2. Find GitHub and click Disconnect if it shows as connected.
3. Click Connect and complete GitHub sign-in again.

Other issues

• github_commit_files says there's nothing to commit. Files need to be edited in the sandbox clone first, with the normal file-editing tools. This tool only pushes whatever is currently there.
• github_create_pull_request failed. Confirm at least one github_commit_files call has already succeeded in this conversation. A pull request needs an existing working branch with at least one commit on it.
• github_upload_file can't find my file. The sandbox path must match a file already in that conversation's sandbox, written by tAI or uploaded earlier in it.
• A new conversation isn't working on the repo I expected. A repo attachment is per conversation. Attach it again from the composer's Connectors menu.