[P1] Restart Discovery button non functional

[frankbria]

When the user is on the dashboard of a project that has already gone through Discovery and have a PRD, clicking the Restart Discovery button doesn't do anything. The screen refreshes sending an API call to the server, but it returns with a 400 error and no edits on the screen.

Console:

error_handler.js:1 Failed to restart discovery: 
Y
501-0fb0225c0fce04a0.js:1 
 POST https://api.dev.codeframeapp.com/api/projects/2/discovery/restart 400 (Bad Request)

error_handler.js:1 Failed to restart discovery: 
Y {message: 'Request failed with status code 400', name: 'AxiosError', code: 'ERR_BAD_REQUEST', config: {…}, request: XMLHttpRequest, …}
code
: 
"ERR_BAD_REQUEST"
config
: 
{transitional: {…}, adapter: Array(3), transformRequest: Array(1), transformResponse: Array(1), timeout: 0, …}
message
: 
"Request failed with status code 400"
name
: 
"AxiosError"
request
: 
XMLHttpRequest
onabort
: 
ƒ ()
onerror
: 
ƒ (t)
onload
: 
null
onloadend
: 
ƒ g()
onloadstart
: 
null
onprogress
: 
null
onreadystatechange
: 
null
ontimeout
: 
ƒ ()
readyState
: 
4
response
: 
"{\"detail\":\"Cannot restart discovery in active phase. Discovery can only be restarted during the discovery phase.\"}"
responseText
: 
"{\"detail\":\"Cannot restart discovery in active phase. Discovery can only be restarted during the discovery phase.\"}"
responseType
: 
""
responseURL
: 
"https://api.dev.codeframeapp.com/api/projects/2/discovery/restart"
responseXML
: 
null
status
: 
400
statusText
: 
""
timeout
: 
0
upload
: 
XMLHttpRequestUpload {onloadstart: null, onprogress: null, onabort: null, onerror: null, onload: null, …}
withCredentials
: 
false
[[Prototype]]
: 
XMLHttpRequest
response
: 
{data: {…}, status: 400, statusText: '', headers: ej, config: {…}, …}
status
: 
400
stack
: 
"AxiosError: Request failed with status code 400\n    at eN (https://dev.codeframeapp.com/_next/static/chunks/501-0fb0225c0fce04a0.js:1:43191)\n    at XMLHttpRequest.g (https://dev.codeframeapp.com/_next/static/chunks/501-0fb0225c0fce04a0.js:1:47640)\n    at tl.request (https://dev.codeframeapp.com/_next/static/chunks/501-0fb0225c0fce04a0.js:1:56133)\n    at async eC (https://dev.codeframeapp.com/_next/static/chunks/app/projects/%5BprojectId%5D/page-216722d1a669bee6.js:1:32361)"
[[Prototype]]
: 
Error

Expected Behavior:
Once the user clicks the Restart Discovery button, there should be a brief confirmation dialogue and the agent re-asks the five discovery questions from the beginning. It restarts the process and erases the old responses and the PRD and generates it from scratch.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#181 - fix(discovery): Allow starting discovery when project is running but discovery idle [merged]
#196 - fix(discovery): Synchronize PRD buttons and fix state persistence on tab revisit [merged]

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[traycerai]

Plan

Observations

The issue occurs because the backend /restart endpoint (file:codeframe/ui/routers/discovery.py, lines 513-518) only allows restarting discovery when the project is in "discovery" phase. However, when discovery completes and PRD is generated, the project transitions to "planning" phase (line 121-123). The frontend shows the "Restart Discovery" button after PRD completion (file:web-ui/src/components/DiscoveryProgress.tsx, lines 771-882), but clicking it results in a 400 error. The current reset_discovery() method (file:codeframe/agents/lead_agent.py, lines 328-370) only resets state to idle without clearing answers or PRD.

Approach

Modify the backend /restart endpoint to support full discovery restart from any phase, implementing a comprehensive reset that clears discovery answers, deletes the PRD, removes generated tasks/issues, resets discovery state to idle, and transitions the project phase back to "discovery". This aligns with the expected behavior where users can restart discovery from scratch even after completing it and generating a PRD. The solution maintains data integrity by performing database operations in the correct order and broadcasting appropriate WebSocket events for real-time UI updates.

Implementation Steps

1. Backend: Enhance Discovery Restart Logic

File: file:codeframe/agents/lead_agent.py

Add a new method full_reset_discovery() that performs comprehensive cleanup:

• Clear all discovery answers from memory table (category='discovery_answers')
• Delete PRD content from memory table (category='prd', key='content' and key='generated_at')
• Reset discovery state to idle (reuse existing logic from reset_discovery())
• Clear answer capture state in DiscoveryAnswerCapture instance

File: file:codeframe/persistence/repositories/activity_repository.py

Add a new method delete_prd(project_id: int) to remove PRD entries:

• Execute SQL: DELETE FROM memory WHERE project_id = ? AND category = 'prd'
• Return boolean indicating success

Add a new method delete_discovery_answers(project_id: int) to remove all discovery answers:

• Execute SQL: DELETE FROM memory WHERE project_id = ? AND category = 'discovery_answers'
• Return boolean indicating success

File: file:codeframe/persistence/database.py

Add delegation methods:

• delete_prd(*args, **kwargs) → delegates to activities.delete_prd()
• delete_discovery_answers(*args, **kwargs) → delegates to activities.delete_discovery_answers()

Add a method delete_project_tasks_and_issues(project_id: int) to remove all tasks and issues:

• Execute SQL: DELETE FROM tasks WHERE project_id = ?
• Execute SQL: DELETE FROM issues WHERE project_id = ?
• Return count of deleted records

2. Backend: Update Restart Discovery Endpoint

File: file:codeframe/ui/routers/discovery.py

Modify the /restart endpoint (lines 477-559):

Remove the restrictive phase validation (lines 513-518) that only allows restart in "discovery" phase.

Add new comprehensive restart logic:

• Check if project exists and user has access (keep existing validation)
• Initialize LeadAgent with API key
• Call agent.full_reset_discovery() to clear all discovery data
• Call db.delete_prd(project_id) to remove PRD
• Call db.delete_project_tasks_and_issues(project_id) to remove tasks/issues
• Update project phase back to "discovery" using db.update_project(project_id, {"phase": "discovery"})
• Broadcast WebSocket event discovery_reset with comprehensive message
• Return success response with state "idle"

Add error handling:

• Wrap operations in try-except to handle partial failures gracefully
• Log detailed error messages for debugging
• Return appropriate HTTP status codes (500 for server errors)

Add confirmation dialogue requirement (mentioned in expected behavior):

• Add optional query parameter confirmed: bool = False
• If not confirmed, return 200 with {"requires_confirmation": true, "message": "This will erase all discovery answers, PRD, and generated tasks. Are you sure?", "data_to_be_deleted": {...}}
• Only proceed with deletion if confirmed=true

3. Frontend: Add Confirmation Dialog

File: file:web-ui/src/components/DiscoveryProgress.tsx

Modify handleRestartDiscovery() function (lines 249-266):

Add confirmation state:

• Add new state: const [showRestartConfirmation, setShowRestartConfirmation] = useState(false)

Update handler logic:

• First call: Show confirmation dialog instead of immediately calling API
• On confirmation: Call API with confirmed=true query parameter
• On cancel: Close dialog and reset state

Add confirmation dialog UI:

• Create a modal/dialog component that appears when showRestartConfirmation is true
• Display warning message: "This will permanently delete all discovery answers, the PRD, and any generated tasks. You'll start from scratch."
• Show two buttons: "Cancel" and "Confirm Restart"
• Style with destructive/warning colors to emphasize the action

Update API call:

• Modify projectsApi.restartDiscovery(projectId) to accept optional confirmed parameter
• Pass confirmed: true when user confirms

4. Frontend: Update API Client

File: file:web-ui/src/lib/api.ts

Update restartDiscovery method (lines 93-96):

• Add optional parameter: confirmed?: boolean
• Include query parameter in request: params: { confirmed: confirmed || false }
• Update TypeScript types to reflect the new parameter

5. Backend: Update Phase Manager Validation

File: file:codeframe/core/phase_manager.py

Update VALID_TRANSITIONS (lines 17-23):

• Ensure "planning" → "discovery" transition is allowed (already present on line 19)
• Add "active" → "discovery" transition to support restart from development phase
• Add "review" → "discovery" transition to support restart from review phase

This ensures phase transitions are valid when restarting discovery from any phase.

6. Testing Considerations

Manual Testing Scenarios:

• Test restart from "planning" phase (after PRD generation)
• Test restart from "active" phase (after task approval)
• Verify confirmation dialog appears and functions correctly
• Verify all data is cleared: discovery answers, PRD, tasks, issues
• Verify project phase resets to "discovery"
• Verify WebSocket events are broadcast correctly
• Test canceling the confirmation dialog
• Test error handling when database operations fail

Edge Cases:

• Restart when discovery is in "idle" state (should be no-op or show message)
• Restart when discovery is in "discovering" state (should clear partial answers)
• Restart with network failures (should show appropriate error)
• Multiple rapid restart clicks (should prevent duplicate operations)

7. WebSocket Event Broadcasting

File: file:codeframe/ui/routers/discovery.py

Update the discovery_reset WebSocket event broadcast (line 536-543):

• Include more detailed information in the event payload
• Add fields: {"type": "discovery_reset", "project_id": project_id, "phase": "discovery", "message": "Discovery has been fully reset. All answers, PRD, and tasks have been cleared.", "cleared_items": {"answers": answer_count, "prd": prd_existed, "tasks": task_count, "issues": issue_count}}

This provides the frontend with detailed information for displaying appropriate feedback to the user.

8. Documentation Updates

User-Facing Documentation:

• Document the restart discovery feature in user guides
• Explain what data is deleted when restarting
• Clarify that this action is irreversible
• Provide use cases for when to restart vs. continue

Developer Documentation:

• Document the new database methods for clearing discovery data
• Update API documentation for the /restart endpoint
• Document the confirmation flow and WebSocket events

Sequence Diagram

sequenceDiagram
    participant User
    participant Frontend
    participant API
    participant LeadAgent
    participant Database
    participant WebSocket

    User->>Frontend: Click "Restart Discovery"
    Frontend->>Frontend: Show confirmation dialog
    User->>Frontend: Confirm restart
    Frontend->>API: POST /api/projects/{id}/discovery/restart?confirmed=true
    API->>Database: Check project exists & user access
    API->>LeadAgent: full_reset_discovery()
    LeadAgent->>Database: DELETE discovery_answers
    LeadAgent->>Database: DELETE prd entries
    LeadAgent->>Database: Reset discovery state to idle
    API->>Database: DELETE tasks & issues
    API->>Database: UPDATE project phase to "discovery"
    API->>WebSocket: Broadcast discovery_reset event
    WebSocket->>Frontend: Receive reset event
    Frontend->>Frontend: Update UI to idle state
    API->>Frontend: Return success response
    Frontend->>User: Show success message

Loading

Import In IDE

🤖 Prompt for AI Agents

## Observations

The issue occurs because the backend `/restart` endpoint (file:codeframe/ui/routers/discovery.py, lines 513-518) only allows restarting discovery when the project is in "discovery" phase. However, when discovery completes and PRD is generated, the project transitions to "planning" phase (line 121-123). The frontend shows the "Restart Discovery" button after PRD completion (file:web-ui/src/components/DiscoveryProgress.tsx, lines 771-882), but clicking it results in a 400 error. The current `reset_discovery()` method (file:codeframe/agents/lead_agent.py, lines 328-370) only resets state to idle without clearing answers or PRD.

## Approach

Modify the backend `/restart` endpoint to support full discovery restart from any phase, implementing a comprehensive reset that clears discovery answers, deletes the PRD, removes generated tasks/issues, resets discovery state to idle, and transitions the project phase back to "discovery". This aligns with the expected behavior where users can restart discovery from scratch even after completing it and generating a PRD. The solution maintains data integrity by performing database operations in the correct order and broadcasting appropriate WebSocket events for real-time UI updates.

## Implementation Steps

### 1. Backend: Enhance Discovery Restart Logic

**File:** file:codeframe/agents/lead_agent.py

Add a new method `full_reset_discovery()` that performs comprehensive cleanup:
- Clear all discovery answers from memory table (`category='discovery_answers'`)
- Delete PRD content from memory table (`category='prd'`, `key='content'` and `key='generated_at'`)
- Reset discovery state to idle (reuse existing logic from `reset_discovery()`)
- Clear answer capture state in `DiscoveryAnswerCapture` instance

**File:** file:codeframe/persistence/repositories/activity_repository.py

Add a new method `delete_prd(project_id: int)` to remove PRD entries:
- Execute SQL: `DELETE FROM memory WHERE project_id = ? AND category = 'prd'`
- Return boolean indicating success

Add a new method `delete_discovery_answers(project_id: int)` to remove all discovery answers:
- Execute SQL: `DELETE FROM memory WHERE project_id = ? AND category = 'discovery_answers'`
- Return boolean indicating success

**File:** file:codeframe/persistence/database.py

Add delegation methods:
- `delete_prd(*args, **kwargs)` → delegates to `activities.delete_prd()`
- `delete_discovery_answers(*args, **kwargs)` → delegates to `activities.delete_discovery_answers()`

Add a method `delete_project_tasks_and_issues(project_id: int)` to remove all tasks and issues:
- Execute SQL: `DELETE FROM tasks WHERE project_id = ?`
- Execute SQL: `DELETE FROM issues WHERE project_id = ?`
- Return count of deleted records

### 2. Backend: Update Restart Discovery Endpoint

**File:** file:codeframe/ui/routers/discovery.py

Modify the `/restart` endpoint (lines 477-559):

**Remove the restrictive phase validation** (lines 513-518) that only allows restart in "discovery" phase.

**Add new comprehensive restart logic:**
- Check if project exists and user has access (keep existing validation)
- Initialize LeadAgent with API key
- Call `agent.full_reset_discovery()` to clear all discovery data
- Call `db.delete_prd(project_id)` to remove PRD
- Call `db.delete_project_tasks_and_issues(project_id)` to remove tasks/issues
- Update project phase back to "discovery" using `db.update_project(project_id, {"phase": "discovery"})`
- Broadcast WebSocket event `discovery_reset` with comprehensive message
- Return success response with state "idle"

**Add error handling:**
- Wrap operations in try-except to handle partial failures gracefully
- Log detailed error messages for debugging
- Return appropriate HTTP status codes (500 for server errors)

**Add confirmation dialogue requirement** (mentioned in expected behavior):
- Add optional query parameter `confirmed: bool = False`
- If not confirmed, return 200 with `{"requires_confirmation": true, "message": "This will erase all discovery answers, PRD, and generated tasks. Are you sure?", "data_to_be_deleted": {...}}`
- Only proceed with deletion if `confirmed=true`

### 3. Frontend: Add Confirmation Dialog

**File:** file:web-ui/src/components/DiscoveryProgress.tsx

Modify `handleRestartDiscovery()` function (lines 249-266):

**Add confirmation state:**
- Add new state: `const [showRestartConfirmation, setShowRestartConfirmation] = useState(false)`

**Update handler logic:**
- First call: Show confirmation dialog instead of immediately calling API
- On confirmation: Call API with `confirmed=true` query parameter
- On cancel: Close dialog and reset state

**Add confirmation dialog UI:**
- Create a modal/dialog component that appears when `showRestartConfirmation` is true
- Display warning message: "This will permanently delete all discovery answers, the PRD, and any generated tasks. You'll start from scratch."
- Show two buttons: "Cancel" and "Confirm Restart"
- Style with destructive/warning colors to emphasize the action

**Update API call:**
- Modify `projectsApi.restartDiscovery(projectId)` to accept optional `confirmed` parameter
- Pass `confirmed: true` when user confirms

### 4. Frontend: Update API Client

**File:** file:web-ui/src/lib/api.ts

Update `restartDiscovery` method (lines 93-96):
- Add optional parameter: `confirmed?: boolean`
- Include query parameter in request: `params: { confirmed: confirmed || false }`
- Update TypeScript types to reflect the new parameter

### 5. Backend: Update Phase Manager Validation

**File:** file:codeframe/core/phase_manager.py

Update `VALID_TRANSITIONS` (lines 17-23):
- Ensure "planning" → "discovery" transition is allowed (already present on line 19)
- Add "active" → "discovery" transition to support restart from development phase
- Add "review" → "discovery" transition to support restart from review phase

This ensures phase transitions are valid when restarting discovery from any phase.

### 6. Testing Considerations

**Manual Testing Scenarios:**
- Test restart from "planning" phase (after PRD generation)
- Test restart from "active" phase (after task approval)
- Verify confirmation dialog appears and functions correctly
- Verify all data is cleared: discovery answers, PRD, tasks, issues
- Verify project phase resets to "discovery"
- Verify WebSocket events are broadcast correctly
- Test canceling the confirmation dialog
- Test error handling when database operations fail

**Edge Cases:**
- Restart when discovery is in "idle" state (should be no-op or show message)
- Restart when discovery is in "discovering" state (should clear partial answers)
- Restart with network failures (should show appropriate error)
- Multiple rapid restart clicks (should prevent duplicate operations)

### 7. WebSocket Event Broadcasting

**File:** file:codeframe/ui/routers/discovery.py

Update the `discovery_reset` WebSocket event broadcast (line 536-543):
- Include more detailed information in the event payload
- Add fields: `{"type": "discovery_reset", "project_id": project_id, "phase": "discovery", "message": "Discovery has been fully reset. All answers, PRD, and tasks have been cleared.", "cleared_items": {"answers": answer_count, "prd": prd_existed, "tasks": task_count, "issues": issue_count}}`

This provides the frontend with detailed information for displaying appropriate feedback to the user.

### 8. Documentation Updates

**User-Facing Documentation:**
- Document the restart discovery feature in user guides
- Explain what data is deleted when restarting
- Clarify that this action is irreversible
- Provide use cases for when to restart vs. continue

**Developer Documentation:**
- Document the new database methods for clearing discovery data
- Update API documentation for the `/restart` endpoint
- Document the confirmation flow and WebSocket events

## Sequence Diagram

```mermaid
sequenceDiagram
    participant User
    participant Frontend
    participant API
    participant LeadAgent
    participant Database
    participant WebSocket

    User->>Frontend: Click "Restart Discovery"
    Frontend->>Frontend: Show confirmation dialog
    User->>Frontend: Confirm restart
    Frontend->>API: POST /api/projects/{id}/discovery/restart?confirmed=true
    API->>Database: Check project exists & user access
    API->>LeadAgent: full_reset_discovery()
    LeadAgent->>Database: DELETE discovery_answers
    LeadAgent->>Database: DELETE prd entries
    LeadAgent->>Database: Reset discovery state to idle
    API->>Database: DELETE tasks & issues
    API->>Database: UPDATE project phase to "discovery"
    API->>WebSocket: Broadcast discovery_reset event
    WebSocket->>Frontend: Receive reset event
    Frontend->>Frontend: Update UI to idle state
    API->>Frontend: Return success response
    Frontend->>User: Show success message
```

---

Execution Information

Branch: main
Commit: ddd386f

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.