feat(harness): apply agent description at harness agent init#633
Merged
Conversation
Adds a `description` field to HarnessConfig (defaulting to the VeADK default description), maps it to the DESCRIPTION env var, and passes it to the Agent constructed at harness startup. This lets a deployed harness carry a configured agent description (e.g. for A2A discovery) instead of always using the default. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The creation-time field set in test_adds_creation_time_fields must list the new `description` field added to HarnessConfig. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The harness agent was always named `harness_agent`, so every deployed harness produced an identically-named A2A agent card. Derive the agent name from the harness name (HARNESS_NAME / app_name) via `agent_name_from_harness`, normalizing it to a valid ADK identifier (ADK requires a Python identifier and forbids "user"; harness names also allow "-" and may start with a digit, e.g. "oauth-test" -> "oauth_test"). Co-Authored-By: Claude Opus 4.8 <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
2 participants
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.
What
Adds a
descriptionfield to the harness agent config so a deployed harness can carry a configured agent description (instead of always the VeADK default).HarnessConfig.description(defaults toDEFAULT_DESCRIPTION)description→DESCRIPTIONenv var (_ENV_FIELDS)description=config.descriptioninto theAgent(...)built at harness startupDESCRIPTIONenv var inagent.pyWhy
Pairs with
agentkit add harness --description/--desc(agentkit-sdk-python). The CLI writesdescriptioninto<name>.harness.json; deploy flattens it toDESCRIPTION; this change makes the harness apply it at agent init (e.g. for A2A discovery).Test
Existing harness tests; the field defaults to the VeADK default description when unset, so behavior is unchanged for existing harnesses.
🤖 Generated with Claude Code