QUESTION #481
-
|
How does AionUi handle context isolation and resource contention when multiple agents and sessions are running in parallel (especially in WebUI remote mode)? For example, what prevents one agent’s filesystem changes, token usage, or context state from affecting another session or tool? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Every CLI tool runs in its own invocation context, with scoped working directories and separate history files, so filesystem operations and prompts don’t bleed between sessions. On the UI side, session metadata and file previews are tracked independently, and resource usage is bounded by the underlying CLI tool rather than a shared agent pool. In WebUI mode, AionUi acts as a controller only, all execution still happens locally on the host machine, and no data or context is transmitted externally. |
Beta Was this translation helpful? Give feedback.
Every CLI tool runs in its own invocation context, with scoped working directories and separate history files, so filesystem operations and prompts don’t bleed between sessions.
On the UI side, session metadata and file previews are tracked independently, and resource usage is bounded by the underlying CLI tool rather than a shared agent pool. In WebUI mode, AionUi acts as a controller only, all execution still happens locally on the host machine, and no data or context is transmitted externally.