From a3c8d1828dcd00cfdf11e7c0f24765fc3f8870d6 Mon Sep 17 00:00:00 2001 From: Mario Zechner Date: Wed, 19 Aug 2026 13:24:17 +0200 Subject: [PATCH] TODOs in lane.ts --- packages/agent/src/harness/runtime2/lane.ts | 3 +++ 1 file changed, 3 insertions(+) diff --git a/packages/agent/src/harness/runtime2/lane.ts b/packages/agent/src/harness/runtime2/lane.ts index 9d2095db7..b0011d23d 100644 --- a/packages/agent/src/harness/runtime2/lane.ts +++ b/packages/agent/src/harness/runtime2/lane.ts @@ -643,6 +643,7 @@ export class Lane implements AgentLane { operation?.state.kind === "run" ? await queuedItems(operation.state.inbox.followUp, "Follow-up entry") : []; + // TODO does a client really need pending writes? We wouldn't visualize those, any other uses for them? const pendingWrites = operation?.state.kind === "run" ? await Promise.all( @@ -669,6 +670,8 @@ export class Lane implements AgentLane { let streamingMessage: NonNullable["streamingMessage"]; let retry: NonNullable["retry"]; let deferred: NonNullable["deferred"]; + // TODO we should always read the full frame list here, assistant messages + // are never humongous const readStreamingMessage = async (responseEntryId: string) => { const frames = []; let cursor: { seq: number } | undefined;