mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Troubleshooting

What to check when MCP AIC will not start, a session will not open or a turn does not behave, matched by the error code you see.

Beta
Start

The server refuses a setting and says which.

A refusal is one line on standard error, ERROR <code>: <message>, and the server exits.

The startup messages and error lines below were captured with MCP AIC 0.2.0 and vary by version.

You seeCauseFix
MCP_AIC_WORKSPACE_ROOTS: is requiredNo folder is allowedSet it to colon-separated absolute folders
every entry must be an absolute pathA root is relativeUse absolute paths
MCP_STUB_SERVER: must be an absolute socket path ...The registry address is relativeGive an absolute path or a URL
data directory unavailable: overlaps an allowed workspace rootThe data folder sits inside a workspace rootMove one of them
data_dir_in_useAnother server already uses that data folderStop it, or give this server its own MCP_AIC_DATA_DIR

Only MCP_STUB_SERVER selects the registry; leave other registry variables unset.

Open

Match the code to the fix.

CodeCauseFix
provider_unavailableThe provider program is not installed, or is not one of Claude, Codex, Cursor and KimiCheck aic_capabilities and install it
invalid_argument: workspace is not allowedThe folder is outside the allowed rootsUse a folder under a root
host_not_isolatedThe server is not in a container and full host access is not acceptedAsk the operator to prepare a suitable environment; review safety and limits before accepting host access
policy_unsupportedThe provider cannot honour native_tools, or its release was not verified for noneCheck the installed release and safety and limits; use a supported provider before accepting broader access or an unverified release
nested_unavailableDocker or the nested image is missingHave the operator restore nested-mode prerequisites; changing to host mode requires an access review
cap_reachedThe session limit is reachedClose a session
Turns

Stuck, refused or empty.

SymptomCauseFix
turn_in_progressA turn is still runningWait with aic_session_read and await_ms, or aic_turn_cancel
steer_unavailableNo provider offers steeringCancel the turn, then send without steer
The agent says it has no toolsNo registry is reachable by the sessionCheck MCP_STUB_SERVER and that the registry runs
not_found for a session that existsIt belongs to another connection, or a reconnect changed your identityCheck the original connection first; list with include_orphaned and resume only when reclaimable
Fewer events than limitRead pages use a 16 KiB target budgetRead on with next_since

When none of these fit, retain the error, session and turn references and ask the operator to check the server log. Inspect partial results and project changes before retrying work. See Safety and limits for what is stored and what a session can reach.