From c4d3984955f35088f5318b9e4636bf610b3fe2f5 Mon Sep 17 00:00:00 2001 From: Richard Levasseur Date: Sun, 25 Oct 2026 14:50:58 -0700 Subject: [PATCH] agents: prompt user via ask_question on sync auth failures Background sync loops that fail due to expired credentials either go unnoticed or get masked by output filtering. Instruct agents in sync-git-branch-continuously to keep the background sync process running, avoid masking authentication errors, prompt the user via ask_question for a UI alert, and verify credentials before signaling an immediate sync. --- .agents/skills/sync-git-branch-continuously/SKILL.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/.agents/skills/sync-git-branch-continuously/SKILL.md b/.agents/skills/sync-git-branch-continuously/SKILL.md index 06f64970e7..466799a76d 100644 --- a/.agents/skills/sync-git-branch-continuously/SKILL.md +++ b/.agents/skills/sync-git-branch-continuously/SKILL.md @@ -84,3 +84,15 @@ To check the status or inspect the output of the active background sync loop: ```bash tail -n 20 "/tmp/sync_git_${REPO_NAME}_${BRANCH_NAME}.log" ``` + +## Authentication Failures + +When `git pull` or `git push` fails due to invalid or expired credentials: + +1. Keep the background sync process running so it automatically resumes if + credentials are refreshed incidentally. Never mask or sanitize + authentication errors to suppress wakeups. +2. Prompt the user via `ask_question` so a UI popup alerts them to + re-authenticate. +3. After the user responds, trigger an immediate sync cycle (`kill -USR1 + `) and verify the sync log.