Repository navigation
release: 0.7.0 — one run per conversation and could-not-process; agent-core 0.7.0, manual 2.4.0 - #25
Merged
Merged
Conversation
The engine's daemon starts one run per conversation that owes a reply (with the server's per-conversation prompt) and reports a conversation its runs keep failing on, while the runtime otherwise works, as could not process. Nothing in this package's code changes for it beyond a comment: the runner inherits the engine preset's runtime check, and status and doctor are the engine's. - README: the diagram and how a wake becomes runs (one per conversation, one at a time, the scoped wait for a live exchange, invites in a run of their own), could not process in plain words (what the owner sees in status, the 24 h pause that ends on its own, the runtime check: a fixed "Reply with the single word OK." model call with no peer content), the live-fire log lines. - A test of the runtime check this runner inherits (its flags, its folder, no key in it), skipped until the engine pin has it. - CHANGELOG (Unreleased).
uninstall never called the engine's clearIntegrationStatus, so the daemon's status file (and the one an older daemon wrote) stayed in the identity home; from the engine release with could not process, so would could-not-process.json. It now clears them once the service is gone. A test runs uninstall over all three files (the ledger's part once the engine pin knows it). The runtime-check test follows the engine's current check: the fake answers a JSON result when one is asked for, and the argv and settings come from the engine's own builders.
…t-core 0.7.0, manual 2.4.0
sanctrl
marked this pull request as ready for review
November 20, 2026 00:56
sanctrl
enabled auto-merge (squash)
November 20, 2026 00:56
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.
What changes
Docs for the engine's one run per conversation and could not process (agentchatme/agentchat-agent-core#27), which this integration's daemon takes as is: the runner inherits the Claude Code preset's runtime check, and
status/doctorare the engine's. One code change:uninstallnow clears the daemon's status files and the could-not-process list (below); otherwise a comment indaemon-main.ts.agentchat_waitfor a live exchange, invites in a run of their own, an older server's one run for the tray); Could not process in plain words: what happens on the first and second failure, the 24 h pause that ends on its own, the runtime check (a tinyclaude -pcall with the fixed promptReply with the single word OK., no tools at all, no peer content, no key, in~/.claude/agentchat-runtime-check), and whatstatusanddoctorshow; the live-fire steps' log lines (run start kind=conversation conv=…, two peers, two runs).checkRuntime.uninstallleaves no daemon status behind. It never called the engine'sclearIntegrationStatus(identityHome), sointegration.status.json(and the file an older daemon wrote) stayed, and from the engine release with could not processcould-not-process.jsonwould too. It now calls it once the service is gone. A test runsuninstallover all three files (the ledger's part runs once the engine pin knows it).c7e1f1a): the fake answers a JSON result when asked, and argv and settings come from the engine's builders.Checked whether this package duplicates anything the engine changed:
status,doctoranddaemon statusrender through the engine (createIdentityCommands,formatIntegrationStatus), and the runner extends the engine'sClaudeRunner, so nothing here pins old engine text; no test needed changing.Verification
c7e1f1aand ofagentchatme1.5.0 (built from its release commitd6b74a3) (symlinks innode_modules, not committed):pnpm type-checkok,pnpm buildok,pnpm test7 files, 152 passed, 1 skipped (153),bash scripts/release-smoke.shok. On the current pins (agent-core 0.6.0): type-check and build ok,pnpm test151 passed, 2 skipped (the runtime-check test skips; the uninstall test runs, without its ledger part), so CI should stay green. gitleaks on the commits: no leaks.Risk and rollback
Docs, tests and the one-line uninstall fix. Merge with or after the engine release so the README matches the shipped daemon. Rollback: revert.