| I apologize for any impression of speculation in my prior response—the phrase "or similar" was imprecise shorthand for the union of message types in the SDK, but all details are grounded in the official documentation. Below, I'll clarify the correlation mechanisms using verified sources from Anthropic's Claude Agent SDK docs (version 1.x series, covering up to the latest as of December 2025). I'll cite directly where relevant. | |
| ### Subagent Invocation and Message Identification | |
| Subagents are invoked via the built-in `Task` tool, which appears as a `tool_use` content block with `name: "Task"` in the streamed messages. This block's `id` (a unique string) serves as the root for the subagent's branch in the agent tree. Once invoked, all subsequent messages from that subagent include a `parent_tool_use_id` field that references this invocation ID, allowing you to logically group them into a branch. Every streamed message (of type `SDKMessage`, which is a union including `SDKAssistantMessage`, `SDKUserMessage`, `SD |
| # Antidote native plugins | |
| getantidote/zsh-defer | |
| # Essential standalone plugins (no OMZ dependency) | |
| zsh-users/zsh-autosuggestions kind:defer | |
| zsh-users/zsh-syntax-highlighting kind:defer | |
| zsh-users/zsh-history-substring-search kind:defer | |
| zsh-users/zsh-completions path:src kind:fpath |
| [env] | |
| TERM = "xterm-256color" | |
| [terminal.shell] | |
| program = "/bin/zsh" | |
| args = ["-l"] | |
| [window] | |
| decorations = "Transparent" | |
| dynamic_title = true |
| raw.githubusercontent.com/openai/openai-openapi/refs/heads/master/openapi.yaml |
| //! Demonstrates either allowing ephemeral mount under AppArmor or avoiding Landlock | |
| //! to prevent conflicts on Ubuntu. If using this approach, ensure the above | |
| //! AppArmor profile is loaded to permit overlay usage. | |
| use std::process::Command; | |
| use std::fs::{create_dir_all, remove_dir_all}; | |
| use std::io::{Write}; | |
| use anyhow::{anyhow, Context, Result}; | |
| use users; |
| //! Demonstrates either allowing ephemeral mount under AppArmor or avoiding Landlock | |
| //! to prevent conflicts on Ubuntu. If using this approach, ensure the above | |
| //! AppArmor profile is loaded to permit overlay usage. | |
| use std::process::Command; | |
| use std::fs::{create_dir_all, remove_dir_all}; | |
| use std::io::{Write}; | |
| use anyhow::{anyhow, Context, Result}; | |
| use users; |
// // MIT License // // Copyright (c) 2025 David Mapledavid@kodegen.ai // // Permission is hereby granted, free of charge, to any person obtaining a copy // of this software and associated documentation files (the "Software"), to deal // in the Software without restriction, including without limitation the rights // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell // copies of the Software, and to permit persons to whom the Software is