Repository navigation
Signals spec: rename 'agent' to 'environment' in descriptions (FI-610) - #1264
Merged
RohithSangati merged 2 commits intoOct 12, 2026
Conversation
Update all descriptive text in Signals OpenAPI spec files to use 'environment' instead of 'agent' when referring to Harness Runtime environments, aligning with product-docs terminology. Field names (agent_id), enum values (source: agent, type: agent), and example values are unchanged — only human-readable descriptions, summaries, and the Signals tag description are updated. 18 files, 42 lines changed.
iamshadmirza
approved these changes
Oct 12, 2026
RohithSangati
approved these changes
Oct 12, 2026
This was referenced Oct 12, 2026
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
4 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.
Summary
Renames the word agent to environment in all Signals OpenAPI spec descriptions, summaries, and the Signals tag description — aligning with the product-docs terminology where Harness Runtime uses "environments" (not "agents").
What changed
agent_idfield names are unchangedsource: agent,type: agent) are unchangedExamples
Context
Follows up on PR #1253 (Signals API endpoints) and aligns with product-docs PR #6776 which already uses "environment" terminology throughout.
Made with Cursor