0.5.23: arXiv and PubMed 429 handling, workflow scripts from files everywhere - #320
Merged
Merged
Conversation
… PubMed 429 once arXiv's API terms ask for one request every three seconds and parallel lookups got 429. PubMed pacing covers one process, but subagents in other processes or a shared IP still drew 429s.
Models still called subagent with workflow: true outside /deepresearch, which fails when the fenced block is only in hidden reasoning, and one run called the script path in parallel with the write that created it.
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
1 participant
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.
From the 2026-10-02 telemetry check:
createRequestPacer, and a 429 is retried once. Live: four parallel ID lookups all succeed in 9.2 s.workflow: true requires exactly one js workflow fenced block(3 installs on 0.5.22, from /lit, /compare, /review and chat, which had no script-file guidance): SYSTEM.md now says to write the script tooutputs/.plans/<slug>-workflow.jsand callsubagentwith that path only after the write succeeds. A first live /lit run called the path in parallel with the write (ENOENT, then recovered); after the tightened wording a second live /lit ran the workflow on the first call, then verifier and reviewer, with every artifact under outputs/.Not in this release: Pi 1.0. pi-btw 0.7.1 (my PR dbachelder/pi-btw#54) allows it, but pi-subagents 0.74.0 cannot start background subagents on Pi 1.0 (
does not provide @earendil-works/pi-agent-core/node, found in a live /lit run). The fix is merged upstream (nicobailon/pi-subagents#2634), unreleased.Verified: tsc, npm test (327 pass; new tests fail before), check-pi-rpc, root and website audits, website build.