Before you begin
AEXGrid runs provider command-line tools under your operating-system account. Install or connect only providers you trust, and choose a workspace folder whose contents are appropriate for the agents you intend to run.
Set up the workspace
- Choose the workspace folder. Plans and agent file operations use this working context.
- Name the workspace and create or rename rooms for distinct streams of work.
- Open Providers & installations to scan the machine, install a supported package, or configure a custom executable.
- Select an empty desk or use + agent; choose the provider, model, effort or mode the provider exposes, and a permission level.
- Use the inspector to send a prompt, watch activity, and interrupt or stop the session when needed.
Choose the right session type
| Session | Use it for |
|---|---|
| Structured agent | Native messages, streamed activity, approvals, configuration, resume support, and coordination tools. |
| Interactive terminal | Any CLI needing a real PTY, keyboard input, ANSI output, scrollback, interrupt, stop, and restart. |
| Custom executable | A literal executable and argument list. Configured values are not interpreted through a shell. |
Choose authority deliberately
Codex sessions distinguish read-only from workspace-write access. Managed workers inherit the launching manager’s workspace-edit choice; a manager role or specialty does not add filesystem, provider, or application permission.
CLI terminals have the permissions of the operating-system user. Process ownership and cleanup are lifecycle controls, not an operating-system sandbox.
Return without auto-launching
AEXGrid restores workspace layout, rooms, launch profiles, task and manager state, plans, and provider-owned conversation references. It does not automatically relaunch saved agents at startup. Resume and restart remain explicit actions.