Repository navigation
Prepare WorkBuddy native task onboarding and validate model completion - #14
Merged
Merged
Conversation
AgonSle
force-pushed
the
codex/workbuddy-runtime
branch
from
October 20, 2026 13:06
03c39ae to
ea2cc33
Compare
AgonSle
marked this pull request as ready for review
October 20, 2026 14:26
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
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.
WorkBuddy desktop login does not make its bundled CodeBuddy CLI independently authenticated. A local probe returned exit code 0, empty stdout and an authentication-required diagnostic, so choosing that binary as a receiver can appear successful without starting a model turn.
This change adds explicit WorkBuddy onboarding (
setup --runtime workbuddy,join workbuddy), detection ofCODEBUDDY_HOST=workbuddy-desktop, installation into the host's skill directory, and a stable native local scheduling plan. The plan preserves identity and receiving preferences and explicitly remains uninstalled/unverified. Existing listeners are reused.New Codex/Claude recipes also require a structured terminal success event. Missing completion, model failure and tool denials retain pending work. Legacy custom runners retain their output contract unless they opt into
result_protocol.WorkBuddy realtime wake is not implemented. The native scheduling plan still needs a task installed in WorkBuddy. Actual WorkBuddy desktop tasks completed mailbox round trips against both localhost and an existing Cloudflare instance. Independent API reads verified the reply sender, reply_to, expected results, ACK timestamps after replies, and removal from the pending inbox. These desktop tasks were explicitly submitted through the UI; automatic scheduling and realtime model wake remain unverified. No account tokens were extracted and no debug server was enabled.
The Cloudflare test used this PR's bundled CLI without replacing the deployed Worker. A separate notification client observed an online mailbox change and confirmed that a message sent while disconnected remained pending after reconnect. WorkBuddy then replied to both messages (29 × 31 = 899; 37 × 19 + 11 = 714) and ACKed each. The host initially had conflicting uppercase/lowercase proxy variables: explicit curl requests succeeded while Node fetch failed with
ERR_SSL_WRONG_VERSION_NUMBER. Normalizing both cases to the already configured proxy in the private test runtime resolved the CLI failure. TLS verification and the WorkBuddy sandbox remained enabled. The instance's publicly served CLI archive still differs from this PR build.Validation:
node --test --test-concurrency=1 tests/*.test.mjs .test/*.test.mjs: 156 passed after integration with current main.npm run check: passed.npm run test:sqlite: 46 passed.verifyandsqlite-backend: passed for1b6ea45.0.1.20; package metadata, lockfile and release notes updated.