📄 File detail

tools/utils.ts

🧩 .ts📏 41 lines💾 1,105 bytes📝 text

🎯 Use case

This module implements the “utils.ts” tool (utils.ts) — something the model can call at runtime alongside other agent tools. On the API surface it exposes tagMessagesWithToolUseID and getToolUseIDFromParentMessage — mainly functions, hooks, or classes. Dependencies touch src.

Generated from folder role, exports, dependency roots, and inline comments — not hand-reviewed for every path.

🧠 Inline summary

import type { AssistantMessage, AttachmentMessage, SystemMessage, UserMessage,

📤 Exports (heuristic)

tagMessagesWithToolUseID
getToolUseIDFromParentMessage

📚 External import roots

Package roots from from "…" (relative paths omitted).

src

🖥️ Source preview

import type {
  AssistantMessage,
  AttachmentMessage,
  SystemMessage,
  UserMessage,
} from 'src/types/message.js'

/**
 * Tags user messages with a sourceToolUseID so they stay transient until the tool resolves.
 * This prevents the "is running" message from being duplicated in the UI.
 */
export function tagMessagesWithToolUseID(
  messages: (UserMessage | AttachmentMessage | SystemMessage)[],
  toolUseID: string | undefined,
): (UserMessage | AttachmentMessage | SystemMessage)[] {
  if (!toolUseID) {
    return messages
  }
  return messages.map(m => {
    if (m.type === 'user') {
      return { ...m, sourceToolUseID: toolUseID }
    }
    return m
  })
}

/**
 * Extracts the tool use ID from a parent message for a given tool name.
 */
export function getToolUseIDFromParentMessage(
  parentMessage: AssistantMessage,
  toolName: string,
): string | undefined {
  const toolUseBlock = parentMessage.message.content.find(
    block => block.type === 'tool_use' && block.name === toolName,
  )
  return toolUseBlock && toolUseBlock.type === 'tool_use'
    ? toolUseBlock.id
    : undefined
}