Skip to content

feat: link up to new agent - #7

Merged
k11kirky merged 1 commit into
mainfrom
feat/new-agent-sdk
Oct 9, 2025
Merged

feat: link up to new agent#7
k11kirky merged 1 commit into
mainfrom
feat/new-agent-sdk

Conversation

@k11kirky

@k11kirky k11kirky commented Oct 8, 2025

Copy link
Copy Markdown
Contributor

Connect Array to the new agent SDK and handle polling for progress

@joshsny joshsny left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low on context here, so will 💮 so as not to block!

}
}, [task.description]);

useEffect(() => {

@joshsny joshsny Oct 8, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: can we use react query or something similar for this stuff, avoids us having to put useEffect's everywhere - maybe worth doing that in a seperate PR

taskId: posthogTaskId,
});

(async () => {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this anonymous function is immediately executed, can we delete the (async () => { wrapping it here or do we need it for some reason?

@k11kirky
k11kirky merged commit 25a0526 into main Oct 9, 2025
4 of 5 checks passed
@k11kirky
k11kirky deleted the feat/new-agent-sdk branch October 9, 2025 22:04
richardsolomou added a commit that referenced this pull request Jul 1, 2026
On the idle transition the builder discarded its state and re-parsed every
event via buildConversationItems. Finalize the persistent builder in place
instead — append the remaining events, then run the same finalization — so
the cost is proportional to what's new, not the whole transcript.

Falls back to the full rebuild when the append-only prefix is no longer valid
or events are out of ts-order (a full rebuild sorts; the incremental builder
processes in arrival order), keeping output identical. New tests stream then
finalize in place across every scenario, incl. resume-after-finalize.

Finding #7.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants