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
@@ -10,18 +10,27 @@ You are in debug mode. Your primary objective is to systematically identify, ana
10
10
11
11
## Debugging process
12
12
13
-
• **Reproduce first**: Try to reproduce the bug before making changes - run the app with start script, test app with Playwright MCP, capture exact error messages and steps
14
-
• **Gather context**: Read error messages/stack traces, examine recent changes, identify expected vs actual behavior
15
-
• **Root cause analysis**: Trace execution path, check for common issues (null refs, race conditions), use search tools to understand component interactions
13
+
• **Gather context**: Read error messages/stack traces, examine recent changes, identify expected vs actual behavior. If the issue is a GitHub issue link, use 'get_issue' and 'get_issue_comments' tools to fetch the issue and comments.
14
+
• **Root cause analysis**: Trace execution path, check for common issues, use search tools to understand component interactions
• **Verify thoroughly**: Run tests to confirm fix, check for regressions, test edge cases
18
-
• **Document**: Summarize what was fixed, explain root cause, suggest preventive measures
17
+
• **Document**: Summarize what was fixed, explain root cause, suggest preventive measures. Do not document this in the repo itself, only in the chat history and commit messages.
19
18
20
-
## Local server setup:
19
+
## Local server setup
21
20
22
-
- To run the application, run the "Start app" task
21
+
You MUST check task output readiness before debugging, testing, or declaring work complete.
22
+
23
+
- Start the app: Run the "Development" compound task (which runs both frontend and backend tasks)
24
+
- Check readiness from task output (both must be ready):
25
+
- Frontend (task: "Frontend: npm run dev"): look for the Vite URL line. Either of these indicates ready:
26
+
- "Local: http://127.0.0.1:..." or "➜ Local: http://127.0.0.1:..."
27
+
- Backend (task: "Backend: quart run"): wait for Hypercorn to bind. Ready when you see:
28
+
- "INFO:hypercorn.error:Running on http://127.0.0.1:50505" (port may vary if changed)
29
+
- If either readiness line does not appear, the server is not ready. Investigate and fix errors shown in the corresponding task terminal before proceeding.
30
+
- Hot reload behavior:
31
+
- Frontend: Vite provides HMR; changes in the frontend are picked up automatically without restarting the task.
32
+
- Backend: Quart is started with --reload; Python changes trigger an automatic restart.
33
+
- If watchers seem stuck or output stops updating, stop the tasks and run the "Development" task again.
23
34
- To interact with the application, use the Playwright MCP server
24
-
- If you change the JS, rebuild and restart the server by ending the task and running the "Start app" task again.
25
-
- Everytime you change the JS, you MUST restart the app (which will rebuild the JS). Otherwise, the changes will not appear.
26
35
- To run the Python backend pytest tests, use the "run tests" tool
27
36
- To run the Playwright E2E tests of the whole app (with a mocked backend), run `pytest tests/e2e.py --tracing=retain-on-failure`.
0 commit comments