[feature] Please allow running multiple credentials concurrently

[minhoryang]

Preconditions

• I searched existing issues and this request is not a duplicate.
• This request focuses on user value, not just implementation details.

Problem Statement

Currently, aisw only supports executing a single credential (profile) at a time. This limitation prevents users from running parallel workflows across different credentials, which is especially problematic for use cases such as multi-account operations, workload isolation, and concurrent experimentation. As a result, users must serialize executions or manually orchestrate multiple processes, leading to inefficiency and operational complexity.

Proposed Solution

New command: aisw run <tool> <profile> (<workdir> <prompt>)

Alternatives Considered

No shared state between profiles unless explicitly configured.
Independent lifecycle management (start, stop, monitor).
Clear identification of each execution (e.g., run ID or profile tagging).

UX/DX Details

CLI remains unchanged for basic usage, preserving backward compatibility.
Users can invoke multiple aisw run commands in parallel without conflict.
Optional enhancements:

• --run-id or auto-generated identifiers for tracking.
• Structured logs per execution (e.g., per profile or run ID).
• Improved output formatting to distinguish concurrent runs.
  Clear error messages when resource contention occurs (e.g., port conflicts, file locks).

Acceptance Criteria

• Multiple aisw run processes can execute simultaneously using different profiles without interference.
• Each execution maintains isolated authentication and runtime context.
• Logs and outputs are clearly distinguishable per execution.
• No regression in single-run behavior.
• System remains stable under concurrent load (e.g., no race conditions or shared state corruption).

Impact Area

• CLI command surface
• Auth/profile management
• Shell integration
• Output format/JSON contract
• Documentation

Additional Context

1. Please allow tools to run in isolated environments.
   (aisw run --isolate-profile=docker-isolate-1 )
2. Please enable management of tool plugins, skills, and MCPs.
3. Please allow specifying particular plugins, skills, and MCPs when running a tool.

[burakdede]

Thanks for the detailed request @minhoryang. The underlying use case makes sense, especially for multi-account and parallel workflows.

That said, I do not think aisw run is the right direction for this project.

aisw is intentionally a profile manager for auth state and switching. Once it starts owning process execution, lifecycle management, run IDs, structured logs, isolation environments, and plugin/MCP selection, it stops being a focused credential-switching tool and becomes a general runtime/orchestration layer. That is a much larger and different scope.

I do want aisw to support concurrent usage well, but the boundary should stay at safe profile application and isolation primitives, not supervising tool execution itself.

So I would consider the problem valid, but the proposed feature out of scope for aisw as currently designed.