@ailog/cli 0.2.6 → 0.3.0

package/README.md

@@ -74,18 +74,16 @@ await createLogger({
 
 Rendered as `key: value` pills on the run header.
 
-### Subagents (shared runId)
+### Subagents (shared threadId)
 
-Group orchestrator and subagent calls under one run by **sharing a `runId`**. Any `aiSdkMiddleware({ runId })` / `createLogger({ runId })` with the same id appends its steps to the same run, in the order they fire. The viewer shows them as one row whose steps tell the whole story.
+Each `aiSdkMiddleware` instance owns one Run automatically. To group orchestrator and subagent calls — each constructed with its own wrapped model — share a `threadId`. They show up side-by-side under the same Thread in the viewer.
 
 ```ts
-import { generateRunId, aiSdkMiddleware } from '@ailog/cli';
-
-const runId = generateRunId();
+import { aiSdkMiddleware } from '@ailog/cli';
 
 const orchestrator = wrapLanguageModel({
   middleware: aiSdkMiddleware({
-    runId,
+    threadId: 'tokyo',
     functionId: 'orchestrator',
     metadata: { userId: '...' },
   }),
@@ -96,8 +94,8 @@ const tools = {
   research: tool({
     execute: async ({ question }) => {
       const sub = wrapLanguageModel({
-        // Same runId → the subagent's step joins the orchestrator's run.
-        middleware: aiSdkMiddleware({ runId }),
+        // Share only the threadId — each tool call gets its own Run in the same Thread.
+        middleware: aiSdkMiddleware({ threadId: 'tokyo', functionId: 'researcher' }),
         model,
       });
       return { answer: (await generateText({ model: sub, prompt: question })).text };
@@ -109,9 +107,9 @@ await generateText({ model: orchestrator, tools, ... });
 ```
 
 Rules:
-- `runId` is auto-generated when omitted.
-- The **first** writer that creates a given run sets its `functionId` / `metadata`; later writers reusing the id keep those values (idempotent).
-- `step_number` is assigned by the DB based on the run's current step count, so concurrent writers within the same process produce a stable monotonic sequence without coordinating.
+- `threadId` is auto-generated (`auto-<short>`) when omitted, so every run still belongs to a Thread.
+- `metadata` lives on the Thread record (not the Run). First-writer-wins: only the call that creates the Thread sets it.
+- Run ids are always auto-generated; you can't reuse one across loggers. Share a Thread, not a Run.
 
 ### Viewer