The Two Phases
Plan Mode (Read-Only)
In Plan Mode, Edgedive analyzes the issue without making any changes to your code.What Happens in Plan Mode
- Reads the issue and any attached context (screenshots, logs, stack traces)
- Explores your codebase to understand the relevant code
- Queries Sentry for error details (if connected)
- Reads related Slack threads for additional context
- Proposes a fix strategy and testing approach
Plan Mode is safe. Edgedive only reads during this phase—no files are modified, no commits are made.
Your Approval
After Plan Mode completes, you receive the plan for review. The plan includes:- Root cause analysis - What Edgedive believes is causing the issue
- Proposed fix - High-level description of the changes
- Files to modify - Which files will be changed
- Testing strategy - How to verify the fix works
| Action | Result |
|---|---|
| Approve | Edgedive proceeds to Execute Mode |
| Request Changes | Provide feedback; Edgedive revises the plan |
| Reject | Stop the process entirely |
Execute Mode (Makes Changes)
Once approved, Edgedive implements the fix.What Happens in Execute Mode
- Creates a new branch from your default branch
- Implements the proposed changes
- Runs your build and test commands
- Commits changes with descriptive messages
- Opens a pull request for review
- Posts the PR link back to the original thread
Session Persistence
Edgedive maintains session state throughout the process. This means:- You can pause and resume investigations
- Context from Plan Mode carries into Execute Mode
- If something fails, Edgedive can retry with the existing context
What Edgedive Has Access To
During analysis and execution, Edgedive can access:| Integration | Access Level | Purpose |
|---|---|---|
| GitHub | Read + Write | Read code, create branches and PRs |
| Linear | Read | Get issue details and context |
| Slack | Read | Read thread history for context |
| Sentry | Read | Fetch error details, stack traces, breadcrumbs |
All integrations except GitHub are read-only. Edgedive only writes to GitHub to create branches and pull requests.
Example Workflow
1
Issue Reported in Slack
“The checkout page crashes when the cart has more than 10 items”
2
Edgedive Enters Plan Mode
- Reads the Slack thread
- Searches codebase for checkout-related code
- Finds the cart handling logic
- Identifies a missing bounds check
3
Plan Posted
“Found the issue:
CartComponent.tsx doesn’t handle arrays > 10 items. Proposed fix: Add pagination to cart display. Testing: Add unit test for large carts.”4
You Approve
Click “Approve” in the Slack thread
5
Edgedive Executes
- Creates branch
fix/cart-pagination - Adds bounds check to
CartComponent.tsx - Adds test in
CartComponent.test.tsx - Runs
npm test - Opens PR with changes
6
PR Ready for Review
Link posted back to Slack: “PR #123 ready for review”