Skip to content

Releases: agents-io/PokeClaw

v0.6.12

30 Apr 17:53

Choose a tag to compare

  • Hotfix for Android background activity launch limits. External automation now has an exported activity entrypoint for MacroDroid, Tasker, and Locale-style apps, avoiding Android 16 / targetSdk 36 background launch blocking when a broadcast receiver tries to open the chatroom.
  • MacroDroid setup now uses Activity target. The verified setup launches io.agents.pokeclaw.automation.ExternalAutomationActivity with RUN_TASK / RUN_CHAT and the same task / chat extras.
  • Broadcast support remains available. The broadcast receiver is still present for ADB and compatible callers, but app-based automation should prefer the Activity target on modern Android.
  • Install note for early testers. If Android reports a package/signature conflict from an older debug or early signed APK, uninstall that old build once and then install this stable signed release.

v0.6.11

30 Apr 17:19

Choose a tag to compare

  • External Automation is now a production feature. PokeClaw exposes user-enabled RUN_TASK and RUN_CHAT Android broadcast entrypoints for MacroDroid, Tasker, Locale-style automation apps, and ADB callers.
  • MacroDroid E2E is verified. A real MacroDroid Send Intent macro successfully triggered PokeClaw, ran how much battery left, and returned the live battery result in the PokeClaw chatroom.
  • External task intents no longer wait on chat model readiness. Task payloads now go straight through the task harness, so deterministic/direct tasks can run even on a clean install with no LLM selected.
  • Direct device-data tasks run before LLM/accessibility gates. Requests such as battery status now use the deterministic device-data tool first instead of being blocked by missing model config when the task does not need an LLM.
  • External Automation has a safe opt-in UI. Settings -> Remote Control -> External Automation is off by default and shows a confirmation before allowing trusted local automation apps to call PokeClaw.
  • Callback contract is in place. RUN_TASK supports immediate accepted and terminal completed / failed / cancelled / blocked / rejected callback statuses when callers provide a return action. True callback-consumer E2E remains open for a Tasker/MacroDroid receiver profile.
  • Product direction is clearer. The README now records the no-PC, phone-resident, local-first harness lane and distinguishes PokeClaw from PC/ADB/cloud mobile-agent frameworks.
  • Install note for early testers. If Android reports a package/signature conflict from an older debug or early signed APK, uninstall that old build once and then install this stable signed release.

v0.6.10

29 Apr 00:21

Choose a tag to compare

  • Model storage hotfix for ROM-specific download failures. PokeClaw now requires the selected model directory to be writable, not merely present, before using it for large .litertlm downloads.
  • External storage fallback is safer. If the external app-files models directory cannot be created or written on a device/ROM, PokeClaw falls back to internal app storage instead of failing later with ENOENT while opening the .downloading file.
  • Bug reports now expose model storage state. Settings -> About -> Report a Bug includes the selected, external, and internal model directories, their readable/writable/stat status, and any storage-selection error.
  • Local model logs are easier to triage. Bug-report logcat capture now includes LocalModelManager, so download/storage failures carry the storage decision path.
  • Release gate is now formalized. QA_CHECKLIST.md now has a per-release gate record template so future releases must explicitly record direction, harness, scope, build/test, artifact, device-smoke, distribution, and user-followup status.
  • Install note for early testers. If Android reports a package/signature conflict from an older debug or early signed APK, uninstall that old build once and then install this stable signed release.

v0.6.9

28 Apr 21:16

Choose a tag to compare

  • Hotfix release for the latest user-reported task failures. This is a focused signed release for fixes that were verified after the v0.6.8 catch-up release; the remaining exploratory QA gaps are still tracked instead of hidden.
  • WhatsApp direct send is more reliable. Literal commands such as send hi to Girlfriend on WhatsApp now route straight to the direct send_message tool, and the focused Pixel 8 Pro regression for the wrong-chat send path now passes.
  • Direct tool execution no longer blocks the app thread. Direct tool tasks now run off the receiver/main path, preserve their real ToolResult, and always clean up task state, which prevents a class of ANR-style failures during quick tasks.
  • Foreground service startup is safer on aggressive Android builds. PokeClaw now enters foreground state immediately when the service is created if notification permission is available, reducing ForegroundServiceDidNotStartInTimeException crashes when a task exits early.
  • WhatsApp contact lookup avoids a false close-button match. The contact picker no longer treats generic top-right image buttons, such as WhatsApp overflow controls, as close buttons unless the UI exposes a clear close/dismiss/cancel signal.
  • QA automation is stricter and cleaner. The quick-task runner now cancels stale tasks between cases, dismisses stale ANR dialogs, waits for Accessibility readiness, resets foreground state, and marks Failed: task answers as real failures.
  • Known remaining QA gaps. The post-fix Cloud sweep was 17 PASS / 0 FAIL / 1 BLOCKED / 2 TIMEOUT / 20 TOTAL; WhatsApp latest-chat summary and copy-latest-email-subject-to-Google still time out, and one call task remains blocked by missing test contact data.
  • Install note for early testers. If Android reports a package/signature conflict from an older debug or early signed APK, uninstall that old build once and then install this stable signed release.

v0.6.8

28 Apr 18:42

Choose a tag to compare

QA note added 2026-04-28: this is a stable-signed catch-up build, not a fully green phone-QA release. Pixel 8 Pro follow-up QA found that some complex automation paths still need work, especially WhatsApp send/chat-summary and local quick-task timeout behavior. Treat v0.6.8 as the current best diagnostic/stable-signed build, not proof that every WhatsApp/local-task issue is fixed. If you are upgrading from an early/debug-signed APK and Android reports a package conflict, uninstall the old APK once and then install this stable-signed build.

  • Stable public catch-up release. This promotes the recent debug-report and local-model hardening work into a stable signed release so users can test one current APK instead of chasing debug prereleases.
  • Model download storage is more reliable. Fixed a device-side failure where the model download directory could be missing on some ROMs, causing downloads to fail with ENOENT before the .litertlm file could even be written.
  • WhatsApp send-message is less likely to hit the wrong action. The send-button matcher now requires either a clear send signal or a button positioned by the composer, which avoids treating top-bar call/video-call buttons as generic send candidates. Follow-up QA still found WhatsApp flows that can timeout or get stuck, so this area remains open.
  • Contact lookup handles blocking popups better. The contact-search flow now attempts to dismiss obvious modal overlays before searching or scrolling the chat list.
  • Foreground service coverage is stronger during tasks and monitoring. PokeClaw now starts foreground status as soon as a task begins, and active monitor mode schedules the watchdog job so ROMs that aggressively kill services have a better recovery path.
  • Bug reports are easier to act on. Settings -> About -> Report a Bug generates a ZIP with app state, filtered logcat, rolling app logs, and recent HTTP logs for device-specific model, download, accessibility, and monitor failures.
  • Release automation is cleaner. Main-branch pushes now build debug artifacts without creating public debug prereleases, while public APK releases go through the signed tag workflow.

Debug Build v0.6.7

18 Apr 19:23

Choose a tag to compare

Debug Build v0.6.7 Pre-release
Pre-release

This is a debug prerelease for bug reporting and support triage.

What changed

  • Settings -> About now has Report a Bug with a GitHub-first flow.
  • Bug reports generate a ZIP locally, then let users choose Open GitHub Issue or Share ZIP.
  • The bundle now includes a bug-report template, filtered app logcat, rolling app logs, and recent HTTP logs.
  • Rolling app logs start at app launch so device-specific failures leave useful breadcrumbs.

Fallback behavior

  • If GitHub login/browser state gets in the way, use Share ZIP and attach the file manually to a GitHub issue.

Verification

  • ./gradlew testDebugUnitTest passed.
  • ./gradlew assembleDebug -x test passed.
  • E2E verified on a connected Pixel 8 Pro with v0.6.7: About shows v0.6.7, Report a Bug builds a fresh ZIP, Open GitHub Issue launches an external GitHub flow, and Share ZIP opens the Android share sheet.

Notes

  • This is still a debug prerelease because the repository is missing Android signing secrets for a stable signed release.

Debug Build v0.6.6

18 Apr 05:57

Choose a tag to compare

Debug Build v0.6.6 Pre-release
Pre-release

Debug Build v0.6.6

This prerelease ships the current bugfix line while stable signing is still blocked by missing GitHub Actions secrets.

Included fixes:

  • adaptive launcher icon resources for OEM/themed launchers
  • stricter local GPU runtime verification and CPU-safe re-arm logic
  • richer debug report state for monitor / notification listener triage
  • stale LocalBackendHealthTest repaired so backend-health unit tests pass again

Validation done locally:

  • ./gradlew testDebugUnitTest passed
  • debug APK installed over an existing PokeClaw build on a physical Pixel 8 Pro
  • app launch smoke test passed on device

Known limitation:

  • GitHub's stable release workflow currently fails because ANDROID_KEYSTORE_B64, ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS, and ANDROID_KEY_PASSWORD are not configured in repo secrets.

Debug Build v0.6.5

14 Apr 00:49

Choose a tag to compare

Debug Build v0.6.5 Pre-release
Pre-release

Full Changelog: v0.6.4...v0.6.5-20260414

v0.6.4

13 Apr 23:07

Choose a tag to compare

Local/OEM hardening release.

Highlights:

  • re-arm verified GPU devices after stale CPU-safe quarantine
  • start Fold 4 local runtime more conservatively
  • richer debug reports for backend/monitor/listener state
  • extra JNI native keep rule for release builds

If your device was previously stuck on CPU after an older local GPU init failure, update to v0.6.4 and try local mode again.

Debug Build v0.6.4

13 Apr 23:09

Choose a tag to compare

Debug Build v0.6.4 Pre-release
Pre-release

Full Changelog: v0.6.3...v0.6.4-20260413