You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Stop operations use PID files (.dev-pids/) instead of pgrep/pkill,
with recursive kill_tree to handle process trees (e.g. yarn->webpack)
- Ports randomized via --randomize-ports flag (default ports unchanged)
- Active ports written to .dev-env.json for agent and tooling discovery
- Go backend auto-recompiles on .go/.mod/.sum changes via inotifywait
with build-then-swap strategy (build to tmp, swap only on success)
- start-console.sh accepts --backend-port, --plugin-port, --console-port,
--cidfile CLI args; uses -p port mapping on all platforms
- webpack.config.ts reads PLUGIN_PORT env var with fallback to 9001
- Agent docs (AGENTS.md, WORKFLOW.md, init-session) reference
.dev-env.json and .dev-logs/
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
description: Run startup sequence (steps 1-6 from docs/WORKFLOW.md)
4
4
---
5
5
@@ -19,5 +19,6 @@ Execute the startup sequence from `docs/WORKFLOW.md`. AGENTS.md is always in con
19
19
3.**Check struggles** — read `docs/agent-struggles.json`. If unresolved entries exist, present to user.
20
20
4.**Pick feature** — read `docs/features.json`, find first `"passes": false` entry.
21
21
5.**Start dev env** — run `./init.sh`.
22
-
6.**Run tests** — run `yarn test` and verify app is healthy.
23
-
7.**Wait** — tell the user you're oriented, report the picked feature and which step of the Feature Development Sequence you'd start at. When the user says to proceed, follow the Feature Development Sequence in `docs/WORKFLOW.md` step by step. Do NOT start any work autonomously.
22
+
6.**Read ports** — read `.dev-env.json` and note the backend, plugin, and console ports.
23
+
7.**Run tests** — run `yarn test` and verify app is healthy.
24
+
8.**Wait** — tell the user you're oriented, report the picked feature and which step of the Feature Development Sequence you'd start at. When the user says to proceed, follow the Feature Development Sequence in `docs/WORKFLOW.md` step by step. Do NOT start any work autonomously.
0 commit comments