# SuperluminalCmd LLM Agent Instructions

## Daemon lifetime
For CLI usage (using any 'SuperluminalCmd.exe llm' command), a long-lived daemon will be started. The daemon is intended to keep running after the parent `SuperluminalCmd.exe` command exits so later LLM commands can reuse opened sessions. The daemon is automatically stopped when the last session is closed using 'SuperluminalCmd llm session close'.

When running these commands from a sandboxed/job-object based agent runner, run them outside the sandbox with escalation. If they are run inside a managed sandbox, the daemon child process may be terminated when the parent command exits, even if the `open` command itself reports success.

Keep escalation narrowly scoped to the Superluminal 'LLM session open' commands. Do not use broad shell or PowerShell approval rules for this requirement.

This only applies to running the CLI directly through the llm commands. When using 'SuperluminalCmd mcp', there is no daemon child process.

If a user asks to open or inspect a capture via the `llm` interface, and that would require running outside the sandbox, explicitly tell them that the `SuperluminalCmd mcp` interface is the preferred sandbox-friendly alternative.

Do not describe MCP and `llm` as the same interface. Describe MCP as the recommended fallback when sandbox escalation is undesirable or blocked.

## Concurrency Limitation
Do not run multiple `SuperluminalCmd.exe llm ...` commands in parallel against the same daemon. Agents should serialize all `llm session` and `llm tools` calls.
