feat(agent-manager): add auto_start_agents configuration to automatically start discovered agents

[Edison-A-N]

Summary

Add auto_start_agents configuration to NetworkConfig that enables automatic startup of all discovered agents during network initialization.

Motivation

• Simplifies debugging workflow: Developers no longer need to manually start agents through the admin interface
• Improves development experience: Agents start automatically when the network initializes, reducing setup time
• Supports automation: Enables automated testing and deployment scenarios where manual agent startup is impractical

Changes

Core Implementation

• Added auto_start_agents boolean field to NetworkConfig (default: False)
• Extended AgentManager.__init__() to accept auto_start_agents parameter
• Implemented AgentManager._auto_start_all_agents() method that:
  • Discovers all agents in the workspace
  • Filters out already running agents
  • Starts remaining agents with 0.5s delay between each
  • Continues on failure (one agent failure doesn't block others)
• Updated Network.__init__() to pass configuration to AgentManager

Testing

• Added comprehensive unit tests (tests/agents/test_agent_manager.py):
  • ✅ Auto-start enabled/disabled scenarios
  • ✅ Filtering of running agents
  • ✅ Empty agent list handling
  • ✅ Error handling and resilience
• All 5 new tests passing
• 875 existing tests passing (no regressions)

Code Quality

• Cleaned up unused imports identified by ruff
• Follows existing project patterns and conventions
• Backward compatible (default False maintains current behavior)

Usage Example

network.yaml

auto_start_agents: true # Enable automatic agent startup

[vercel]

@Edison-A-N is attempting to deploy a commit to the Raphael's projects Team on Vercel.

A member of the Team first needs to authorize it.