Skip to content

Refactor: Rename "agent" domain to "operator" across client SDK#118

Merged
jfrench9 merged 1 commit into
mainfrom
refactor/ai-operator-agent
May 17, 2026
Merged

Refactor: Rename "agent" domain to "operator" across client SDK#118
jfrench9 merged 1 commit into
mainfrom
refactor/ai-operator-agent

Conversation

@jfrench9
Copy link
Copy Markdown
Member

Summary

This PR performs a comprehensive domain terminology refactor, renaming all "agent" concepts to "operator" throughout the robosystems_client SDK. The change spans API endpoints, client classes, data models, and tests — affecting 36 files with a consistent, mechanical rename.

Key Accomplishments

  • API layer: Renamed the api/agent/ module to api/operator/, including all endpoint functions:

    • auto_select_agentauto_select_operator
    • execute_specific_agentexecute_specific_operator
    • get_agent_metadataget_operator_metadata
    • list_agentslist_operators
    • recommend_agentrecommend_operator
    • batch_process_queries updated to use operator terminology
  • Client layer: Renamed AgentClient to OperatorClient (agent_client.pyoperator_client.py) with all method signatures and internal references updated. The facade client is updated to expose the new naming.

  • Models layer: Renamed all 18+ model classes from Agent* to Operator* (e.g., AgentRequestOperatorRequest, AgentResponseOperatorResponse, AgentRecommendationOperatorRecommendation, etc.), including nested/auxiliary types for context, metadata, error details, and tokens used.

  • Public exports: Updated clients/__init__.py and models/__init__.py to export the renamed symbols.

  • Extension operations: Updated references in op_auto_map_elements.py and op_create_mapping_association.py to align with the new operator terminology.

  • Tests: Renamed test_agent_client.py to test_operator_client.py with all test cases updated to reference operator models and client methods.

Breaking Changes

⚠️ This is a breaking change for all consumers of the SDK.

  • All Agent* model classes have been removed and replaced with Operator* equivalents.
  • AgentClient no longer exists; consumers must migrate to OperatorClient.
  • API module path changed from robosystems_client.api.agent to robosystems_client.api.operator.
  • Any code importing agent-related symbols from robosystems_client.models or robosystems_client.clients will need to be updated.

Downstream services and integrations must be updated in coordination with this change.

Testing Notes

  • All existing agent client tests have been migrated to test_operator_client.py with updated class/method/model references.
  • Test coverage is preserved — this is a rename-only refactor with no behavioral changes to business logic.
  • Verify that no downstream consumers still reference the old agent imports before merging.

Infrastructure Considerations

  • Any CI/CD pipelines or configuration that reference the old module paths (api.agent, AgentClient) will need corresponding updates.
  • If the SDK is published as a package, this constitutes a major version bump due to the breaking API surface change.
  • Dependent services should be identified and coordinated for a synchronized rollout.

🤖 Generated with Claude Code

Branch Info:

  • Source: refactor/ai-operator-agent
  • Target: main
  • Type: feature

Co-Authored-By: Claude noreply@anthropic.com

- Implemented OperatorRecommendationRequestContextType0 model for handling recommendation request context.
- Created OperatorRecommendationResponse model to encapsulate operator recommendations and query details.
- Developed OperatorRequest model for managing operator requests with various attributes including message, history, context, and selection criteria.
- Introduced OperatorResponse model to represent responses from operator interactions, including content, metadata, and execution details.
- Added error handling with OperatorResponseErrorDetailsType0 and metadata with OperatorResponseMetadataType0.
- Implemented token usage tracking with OperatorResponseTokensUsedType0.
- Updated SelectionCriteria model to reflect operator selection criteria, including capabilities and preferred modes.
- Created comprehensive unit tests for OperatorClient and its associated dataclasses to ensure functionality and reliability.
@jfrench9 jfrench9 merged commit b1395f5 into main May 17, 2026
1 check passed
@jfrench9 jfrench9 deleted the refactor/ai-operator-agent branch May 17, 2026 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant