gaslighting-engine 0.3.0 → 0.4.0

package/README.md

@@ -22,29 +22,27 @@ They say "the rest follows the same pattern."
 
 Gaslighting-engine is a strict project-discipline generator that stops this behavior.
 
-It generates:
-
-- `.gaslighting/GASLIGHTING.md`
-- `.gaslighting/PRD.md`
-- `.gaslighting/ASSUMPTIONS.md`
-- `.gaslighting/MISSING_INFO.md`
-- `.gaslighting/DECISION_LOG.md`
-- `.gaslighting/MEMORY.md`
-- `.gaslighting/AGENT_RUNTIME.md`
-- `.gaslighting/STACK_POLICY.md`
-- `.gaslighting/PROJECT_CARE.md`
-- `AGENTS.md`
-- `.gaslighting/CODEX_PROMPT.md`
-- `.codex/prompts/gaslighting.md`
-- Codex Skill files
+It now has two layers:
+
+- CLI discipline generator
+- Codex-style local Mission Control desktop app
+
+It writes the heavy project-control system under `.gaslighting/`, keeps root `AGENTS.md` short, and uses `.agents/` as the shared source-of-truth for skills, MCP definitions, prompts, and runtime config.
 
 ## Quick Start
 
 ```bash
-npx gaslighting-engine@latest start "I want to build a hospital website."
+npx gaslighting-engine@latest desktop "I want to build a hospital website."
 ```
 
-This generates the discipline documents, opens the local Mission Control GUI, and prepares a Codex launch command.
+This opens Gaslighting Mission Control, where you can review the mission, choose the agent runtime, select permission mode, generate the structured docs, and start the agent.
+
+Headless CLI flow:
+
+```bash
+npx gaslighting-engine@latest "I want to build a hospital website."
+npx gaslighting-engine@latest run "I want to build a hospital website."
+```
 
 Short aliases after global install or local link:
 
@@ -87,9 +85,20 @@ gaslighting init "I want to build a hospital website."
 gaslighting-engine generate "Build an ecommerce MVP."
 gaslighting-engine update "The hospital is actually an OB-GYN clinic, not dermatology."
 gaslighting-engine doctor
+gaslighting-engine desktop "Build a hospital homepage"
 gaslighting-engine start "Build a hospital homepage"
 gaslighting-engine cockpit
 gaslighting-engine run "Build a hospital homepage"
+gaslighting-engine agent list
+gaslighting-engine loop start "Build a hospital homepage"
+gaslighting-engine loop status
+gaslighting-engine loop resume
+gaslighting-engine loop stop
+gaslighting-engine mcp search github
+gaslighting-engine mcp install github --runtime codex
+gaslighting-engine mcp list
+gaslighting-engine skill create hospital-homepage
+gaslighting-engine skill install hospital-homepage --runtime codex
 gaslighting-engine upgrade
 gaslighting-engine codex-install
 gaslighting-engine codex-doctor
@@ -105,7 +114,58 @@ Gaslighting-engine keeps project-control documents in `.gaslighting/` by default
 
 Only root `AGENTS.md` is written at the top level because Codex expects project guidance there. It is a thin pointer into `.gaslighting/`.
 
-## Mission Control
+```txt
+.gaslighting/
+  INDEX.md
+  mission/
+  product/
+  pages/
+  features/
+  operations/
+  decisions/
+  tasks/
+  loops/
+  verification/
+  memory/
+
+.agents/
+  config.json
+  skills/
+  prompts/
+  mcp/
+  runtimes/
+```
+
+Runtime-specific files such as `.codex/skills`, `.codex/prompts`, and `.codex/config.toml` are exports from `.agents/`.
+
+## Desktop Mission Control
+
+```bash
+npx gaslighting-engine@latest desktop "I want to build a hospital website."
+```
+
+Mission Control is an Electron app with a Codex-style project surface:
+
+- project request input
+- generated mission and PRD preview
+- runtime selector: Codex, Claude Code, Qwen Code, Kimi-compatible, OpenCode, OpenAI-compatible, local
+- model picker when the runtime supports it
+- permission mode selector
+- Mission Loop toggle
+- Git/GitHub/domain/deploy/env health panel
+- MCP search/install panel
+- shared skill create/install panel
+- integrated terminal/log panel
+
+Permission modes:
+
+- `ask_each_task`: ask before each task and sensitive operation
+- `auto_review`: default; normal work proceeds, sensitive operations require approval
+- `full_autonomy`: run without approval, still log checkpoints and avoid leaking secrets
+
+Mission Loop is OFF by default. When enabled, it runs task by task, writes checkpoints, records iteration logs, and refuses to mark failed verification as complete.
+
+## Legacy Web Cockpit
 
 Mission Control is the Codex-first GUI agent surface:
 
@@ -122,6 +182,20 @@ It shows:
 - Codex runtime args
 - Start Codex action
 
+By default, `Start Codex` closes the local cockpit server and continues Codex in the same terminal that launched Mission Control. This keeps Cursor, Warp, Windows Terminal, or any other terminal flow intact.
+
+If you explicitly want a separate terminal, add:
+
+```bash
+npx gaslighting-engine@latest start "I want to build a hospital website." --new-terminal
+```
+
+To customize Codex flags, use:
+
+```bash
+npx gaslighting-engine@latest start "I want to build a hospital website." --codex-args="--search --dangerously-bypass-approvals-and-sandbox"
+```
+
 Open it for an existing project:
 
 ```bash
@@ -134,6 +208,61 @@ Run without the GUI:
 npx gaslighting-engine@latest run "I want to build a hospital website."
 ```
 
+## Agent Runtimes
+
+Check local runtime availability:
+
+```bash
+npx gaslighting-engine@latest agent list
+```
+
+The runtime abstraction separates model switching from long-running loops.
+
+- Codex, Claude Code, Qwen Code, and OpenCode use their own CLI model settings.
+- Kimi can be used through compatible CLI or OpenAI-compatible flows.
+- OpenAI-compatible direct mode uses `OPENAI_COMPATIBLE_API_KEY`, `OPENAI_API_KEY`, or `KIMI_API_KEY`.
+- Local mode expects `ollama`.
+
+## Mission Loop
+
+```bash
+npx gaslighting-engine@latest loop start "Build a hospital homepage"
+npx gaslighting-engine@latest loop status
+npx gaslighting-engine@latest loop resume
+npx gaslighting-engine@latest loop stop
+```
+
+Loop state is stored in:
+
+```txt
+.gaslighting/tasks/
+.gaslighting/loops/
+.gaslighting/checkpoints/
+.gaslighting/verification/
+```
+
+The loop does not replace judgment. It gives the agent a repeatable task runner with checkpoint memory and verification gates.
+
+## MCP And Skills
+
+Search and install MCP definitions:
+
+```bash
+npx gaslighting-engine@latest mcp search github
+npx gaslighting-engine@latest mcp install github --runtime codex
+npx gaslighting-engine@latest mcp doctor
+```
+
+Create a shared project skill and export it to Codex:
+
+```bash
+npx gaslighting-engine@latest skill create hospital-homepage
+npx gaslighting-engine@latest skill install hospital-homepage --runtime codex
+npx gaslighting-engine@latest skill doctor
+```
+
+Shared source files live in `.agents/`. Runtime exports are generated from there.
+
 ## Project Care
 
 Gaslighting-engine also writes `.gaslighting/PROJECT_CARE.md`.