Document agent name customization for the Claude Code plugin#2760
Merged
Conversation
Adds docs for the agent_name setting and WEAVE_AGENT_NAME env var introduced in wandb/weave-claude-code#89, which lets users rename the top-level agent shown in Weave's Agents view (default: claude-code). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
📚 Mintlify Preview Links📝 Changed (1 total)📄 Pages (1)
🤖 Generated automatically when Mintlify deployment succeeds |
Contributor
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Checked against: https://wb-21fd5541-weave-claude-code-agent-name-89.mintlify.app |
…nt-name-89 # Conflicts: # weave/guides/integrations/agents/claude-code-harness.mdx
anastasiaguspan
approved these changes
Jun 15, 2026
ngrayluna
pushed a commit
that referenced
this pull request
Jun 15, 2026
## Summary Documents the customizable `agent_name` setting and `WEAVE_AGENT_NAME` environment variable added in [wandb/weave-claude-code#89](wandb/weave-claude-code#89). This lets users rename the top-level agent shown in Weave's Agents view instead of the hardcoded `claude-code` default. Changes to `weave/guides/integrations/agents/claude-code-harness.mdx`: - **Configure the plugin**: add a `config set agent_name` example, a `WEAVE_AGENT_NAME` env var export, and a short explanation (default `claude-code`, can't be empty, whitespace trimmed). - **Trace tree**: note that the root `invoke_agent claude-code` span uses the configurable top-level agent name, and that subagents keep their own type names. - **Weave skills**: add `agent_name` to the `/weave:weave-config set` examples. ## Notes - Edits target the harness doc, which tracks the current `weave-claude-code` CLI (matching the PR repo's naming, the Agents view, and the `invoke_agent` span names). - The older `weave/guides/integrations/claude_code.mdx` page documents a differently-named `weave-claude-plugin` incarnation and was left untouched. Worth a follow-up if that page is still meant to be current. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the customizable
agent_namesetting andWEAVE_AGENT_NAMEenvironment variable added in wandb/weave-claude-code#89. This lets users rename the top-level agent shown in Weave's Agents view instead of the hardcodedclaude-codedefault.Changes to
weave/guides/integrations/agents/claude-code-harness.mdx:config set agent_nameexample, aWEAVE_AGENT_NAMEenv var export, and a short explanation (defaultclaude-code, can't be empty, whitespace trimmed).invoke_agent claude-codespan uses the configurable top-level agent name, and that subagents keep their own type names.agent_nameto the/weave:weave-config setexamples.Notes
weave-claude-codeCLI (matching the PR repo's naming, the Agents view, and theinvoke_agentspan names).weave/guides/integrations/claude_code.mdxpage documents a differently-namedweave-claude-pluginincarnation and was left untouched. Worth a follow-up if that page is still meant to be current.