feat(telegram): human-realistic wait defaults for ask/poll - #336
Merged
Conversation
…ezing Distilled from the attention-engine ADR-0011 session: an adversarial test construction (discriminator, stress case, gate) is unverified until a deterministic simulation of the exact charged mechanism shows decisive broken-vs-correct separation on every seed, carried forward by meta-tests. The session fired the rule three times (refuted first-draft discriminator, omitted 1/sqrt(d) scale, wrong noise model at calibration). Path-scoped to test/ADR authoring surfaces per the context-budget gate. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SZErTem91K3hperVX4ffR3
telegram-ask and telegram-poll gave up after 5 minutes, with the first reminder nudge 30s after the question — unrealistic for a human who is away from their phone. Raise the default timeout to 1 hour and start the exponential reminder backoff at 5 minutes (5m, 10m, 20m, capped by the deadline). Update the telegram skill to match: document the new defaults and add the run_in_background calling pattern, since the 1-hour default now exceeds the Bash tool's 10-minute foreground timeout cap. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LpXfWJDmEAgZ29o7Kkj9Ff
github-actions
Bot
added
documentation
Contributor
|
| Status | Count |
|---|---|
| 🔍 Total | 170 |
| ✅ Successful | 160 |
| ⏳ Timeouts | 0 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 9 |
| ❓ Unknown | 0 |
| 🚫 Errors | 1 |
Errors per input
Errors in exact_dot_claude/docs/prds/daily-catchup.PRD.md
- [404] https://docs.anthropic.com/claude-code/commands | Failed: Network error: Not Found
Full Github Actions output
Please fix the broken links before merging.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
telegram-ask/telegram-poll: default timeout raised 300s → 3600s (1 hour); first reminder nudge raised 30s → 5 minutes, still doubling exponentially (5m → 10m → 20m, capped by the deadline).telegramskill: documents the new defaults and adds therun_in_background=truecalling pattern, since the 1-hour default now exceeds the Bash tool's 10-minute foreground timeout cap.Why
The old defaults nudged at ~30s/90s/210s and gave up at 5 minutes — not realistic for a human away from their phone. Reminders now back off on human timescales and the wait survives a coffee break.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LpXfWJDmEAgZ29o7Kkj9Ff