-
Notifications
You must be signed in to change notification settings - Fork 2
Comparing changes
Open a pull request
base repository: littlebearapps/untether
base: v0.34.2
head repository: littlebearapps/untether
compare: v0.34.3
- 7 commits
- 26 files changed
- 2 contributors
Commits on Mar 8, 2026
-
fix: v0.34.3 — tool-aware stall threshold, edit failure recovery, dia…
…gnostics (#103, #104, #105, #89) - Tool-aware stall threshold: 10 min when a tool is actively running (#105) - Progress edit failure fallback: log + send when initial edit fails (#103) - Approval keyboard: wait=True for keyboard transitions, failure logging (#104) - /usage 429: downgrade from error to warning level (#89) - Session cleanup structured reporting, spawn args logging, no-events warning - 300+ lines of new tests, integration testing playbook Co-Authored-By: Claude Opus 4.6 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for fe18aeb - Browse repository at this point
Copy the full SHA fe18aebView commit details -
docs: document MCP-automated integration testing across rules, skills…
…, and guides Integration tests are now automated via Telegram MCP tools (send_message, get_history, list_inline_buttons, press_inline_button, reply_to_message). Updated all relevant docs to reflect this workflow. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 8d0265e - Browse repository at this point
Copy the full SHA 8d0265eView commit details -
docs: all integration test tiers fully automatable by Claude Code
- T1 (voice): send_voice MCP tool with OGG/Opus file - T5 (media groups): send_file MCP tool for rapid file sends - B4 (SIGTERM): Bash tool kill -TERM - B5 (log inspection): Bash tool journalctl + FD/zombie checks - Add post-test log inspection and GitHub issue creation instructions - Add structured test result tracking (pass/fail/error with reason) - Distinguish Untether bugs from upstream engine API errors Co-Authored-By: Claude Opus 4.6 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for af5d270 - Browse repository at this point
Copy the full SHA af5d270View commit details -
docs: remove remaining "manual" references from integration testing docs
All tiers are fully automatable — no manual steps remain. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 80bb058 - Browse repository at this point
Copy the full SHA 80bb058View commit details -
docs: add unexpected engine behaviour detection to integration testing
Watch for phantom responses (output from empty input), session cross-contamination, wrong engine, disproportionate cost. Discovered via AMP producing substantive DNS content from empty voice transcription. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for aa996b1 - Browse repository at this point
Copy the full SHA aa996b1View commit details -
docs: comprehensive doc audit — test counts, engine lists, MCP tools
- CLAUDE.md: update test counts (1472→1548), add test_build_args.py and test_loop_coverage.py, add send_voice/send_file to MCP list - AGENTS.md: Gemini CLI and Amp are shipped, not "coming soon" - CONTRIBUTING.md: add gemini/amp to architecture diagram and prereqs - hooks.json: add MCP automation note to version bump checklist - testing-conventions.md: add new test files to key test table - integration-testing.md: add T5 send_file limitation note Co-Authored-By: Claude Opus 4.6 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 5f9fe13 - Browse repository at this point
Copy the full SHA 5f9fe13View commit details -
Merge pull request #106 from littlebearapps/fix/v0.34.3
fix: v0.34.3 — tool-aware stall threshold, edit failure recovery, diagnostics
Configuration menu - View commit details
-
Copy full SHA for feeaac6 - Browse repository at this point
Copy the full SHA feeaac6View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.34.2...v0.34.3