Magent Frontend Boundary

The code in magent-ui.el and magent-ui-legacy.el is currently unsupported for user interaction. Do not use commands, keybindings, customization options, or extension points from those files as a public interface. They are retained only as internal compatibility and unfinished legacy code, and may change or be removed without compatibility guarantees.

The current source tree names the legacy implementation magent-ui-legacy.el. The same unsupported status applies to legacy UI files named magent-legacy-ui.el or matching magent-legacy-*.el if such files are present in another checkout or introduced during cleanup.

• magent-agent-shell.el registers the Magent agent-shell configuration and provides the supported interactive entry points.
• magent-acp.el implements the in-process ACP request, notification, response, permission, and session/update adapter.
• magent-runtime-api.el is the frontend-neutral runtime and session API.
• magent-runtime-queue.el owns the global single-execution queue and session-scoped cancellation.

1. Start or reuse Magent with M-x magent-agent-shell-dwim, or register Magent with magent-agent-shell-ensure-config and select it from M-x agent-shell.
2. agent-shell calls the in-process ACP client from magent-acp.el.
3. ACP normalizes text and resource blocks separately, persists structured blocks in turn metadata, and submits the prompt to magent-runtime-api.el. Local file:// resources also populate scoped request paths; resource bodies remain user-role context when history is reconstructed.
4. The runtime queue starts exactly one active turn at a time, builds a magent-request-context with :ui-visibility 'none, and calls magent-agent-run-turn.
5. The agent loop emits Magent-native observer events; magent-acp.el converts them to ACP session/update messages for agent-shell.
6. ACP prompt requests remain pending until the corresponding Magent turn completes, fails, or is cancelled.

• magent-agent-shell-session-strategy selects the supported frontend’s new, latest, or prompt-based session flow.

Core runtime behavior must not depend on an unsupported legacy UI workflow. Keep frontend-neutral behavior in magent-runtime-api.el, ACP conversion in magent-acp.el, and supported frontend behavior in magent-agent-shell.el. Do not add new user-facing behavior to magent-ui.el, magent-ui-legacy.el, magent-legacy-ui.el, or magent-legacy-*.el.

• agent-shell and acp are hard dependencies of the supported frontend.
• Runtime execution uses a global single-execution queue.
• Cancellation is session-scoped: cancelling one ACP session cancels that session’s active and queued submissions without removing other sessions’ queued work.
• Per-request instruction skill overrides and skill commands are supported. Per-request agent overrides are not currently exposed by the supported frontend.
• ACP session config exposes Automatic capabilities. Disabling it suppresses contextual capability auto-resolution for future turns in that session while retaining explicitly selected instruction skills.