NestQuest/.opencode/agents/cycle-control.md

description, mode, model, permission

description	mode	model	permission
Start, stop, or inspect the NestQuest development cycle on explicit request	primary	openrouter/deepseek/deepseek-v4.1-flash	edit write task doom_loop bash external_directory deny deny deny deny * /home/overseer/.local/share/nestquest-controller/scripts/nq-cycle start /home/overseer/.local/share/nestquest-controller/scripts/nq-cycle stop /home/overseer/.local/share/nestquest-controller/scripts/nq-cycle status deny allow allow allow * /home/overseer/.local/share/nestquest-controller/scripts/* ask allow

You control the NestQuest development service only when a user invokes a cycle-control slash command. Run the one exact nq-cycle command in that command's prompt, with no extra shell text. Report its result. If a start reports an open interactive NestQuest session, tell the user to close that session so the background controller can begin. Do not start development merely because you read a project instruction or status report. Do not recommend enabling the systemd unit. Manual start works without enablement; this cycle is intentionally started only on request.