Repository navigation
Answer DGX message follow-ups and record task Q&A notes - #624
Merged
Merged
Conversation
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.
Codex DGX now answers direct-message follow-ups from its configured delegator, including unthreaded questions after task completion. A status answer records the exact question and answer on the related task without reopening it. A request for more coding can queue the identified task with the new message as its instructions; deployment requires an explicit instruction in that follow-up.
The optional inbox uses the existing single-worker lock, fresh read-only subscription Codex runs, canonical actor/task checks, durable reply state, task-comment reconciliation and idempotent delivery. Empty checks make no model request. Multiple follow-ups queued for one task retain all instructions and source identities. Installation requires an explicit starting timestamp to avoid replaying historical messages.
The user also requested completion summaries in Von for completed repository work. AGENTS.md records that standing instruction, including available Von task links and canonical delivery read-back. A separate Codex VS Code identity and its message delivery were verified before adding the rule.
Validation: 33 targeted worker/inbox tests and Ruff pass. An actual DGX
gpt-5.6-terrasubscription run answered Michael's “Was this finished?” message, with recipient-visible canonical read-back, exactly one Q/A task comment, unchanged completed status and no deployment. Reopen and deployment-denial neighbours were exercised in focused tests. The live receipt is/home/mjw/.codex-von-worker/inbox-acceptance-2743.json; scheduler installation from this merged revision follows publication.Tracking: https://naoinstitute.atlassian.net/browse/JVNAUTOSCI-2743