Skip to main content
After Edgedive completes an investigation, you can take action. Every handoff option includes the full investigation context so nothing is lost.
Handoff OptionBest For
One-Click PRStraightforward fixes Edgedive can implement directly
CLI Local TakeoverWhen you want to continue the investigation or fix locally

​
What Context Gets Passed

Every handoff includes the full investigation output:
  • Root cause findings — What went wrong and why
  • Relevant logs — Key log entries with timestamps
  • Impact analysis — Affected users, services, and severity
  • Commit context — Recent code changes related to the issue
  • Investigation timeline — Sequence of events and evidence
  • Suggested remediation — Recommended fix approach
This context means the downstream agent or engineer starts with full production understanding—no manual log retrieval or context building required.

​
One-Click PR

Edgedive can implement a fix and open a pull request directly from the investigation.
1

Review the Investigation

Edgedive posts its root cause analysis and suggested fix to Slack
2

Approve the Fix

Click Approve in the Slack thread or Linear comment
3

PR Created

Edgedive creates a branch, implements the fix, runs your build/test scripts, and opens a PR
Always review the investigation and proposed fix before approving. Edgedive works best with human oversight.

​
What Edgedive does during execution

  1. Creates a branch from your default branch (e.g., edgedive/fix-checkout-timeout)
  2. Implements the proposed changes
  3. Runs pre/post execution scripts (if configured)
  4. Commits with descriptive messages
  5. Opens a pull request and posts the link back to the original thread
Requires GitHub to be connected with write access to the target repository.

​
CLI Local Takeover

Continue an investigation or fix locally using the Edgedive CLI with Claude Code. Full session context is synced to your terminal.

​
Installation

npm install -g @edgedive/cli
Then authenticate: 
dive login
Both dive and edgedive commands work identically.

​
Usage

1

Find the Investigation

Go to Issues in Edgedive and select an investigation
2

Copy the Command

Look for Take over Claude session locally and copy the command
3

Run Locally

Paste and run from your repository directory:
dive local --issue-url <linear-issue-url>
4

Work and Close

When you’re done, close the session—context syncs back to Edgedive automatically
You must be in the target repository directory when running this command.

​
Other URL types

# From a GitHub PR
dive local --pr-url <github-pr-url>

# From a Slack thread
dive local --thread-url <slack-thread-url>

# From an Asana task
dive local --task-url <asana-task-url>

# From a shared session
dive local --session-url <session-url>

​
Worktree mode

Create an isolated worktree instead of checking out in your current repository: 
dive local --issue-url <url> --worktree

​
Context sync

When you close your local session:
  • Your progress is automatically uploaded back to Edgedive
  • The cloud agent can pick up where you left off
  • Full conversation history is preserved
This enables flexible workflows—start in Edgedive, continue locally, then hand back to Edgedive as needed.