Autonomous Bug Bounty Operations

The depth your next finding demands.

RedDepth turns OpenCode into a visible, exhaustive penetration-testing workflow—scope-locked, evidence-backed, and always under your control.

OpenCode-native Foreground only Scope first
reddepth / campaign live
~/ engagements/oceanic 14:32:08 UTC
CURRENT OBJECTIVEExpand authenticated surface
ACTIVE
68%coverage
0completion predicate100
RECENT SURFACESDISPOSITION
api.oceanic.dev/v2/teams/:idmapped
app.oceanic.devrecovery flowrevisit
files.oceanic.devsigned uploadshypothesis
validator reproduced a role boundary anomaly
All actions visible to operatorscope_ref: ocn-7f2
Operator view01 / 03
Built for investigations where
“no findings yet” isn’t a conclusion.
Evidence before conclusionRaw observations stay intact.
Re-entry by evidenceNew signals reopen old paths.
Human in the loopApprove, redirect, or stop.
The RedDepth method

Not a faster scan.
A deeper loop.

Every surface becomes an obligation. Every anomaly becomes a bounded hypothesis. Every reportable finding gets a second set of eyes.

01 SURFACE

Map the whole surface

Routes, roles, workflows, trust boundaries, and the relationships hiding between them—kept in a living coverage ledger.

Explore the ledger
02 HYPOTHESIS

Follow the signal

New credentials, errors, or state changes can reopen an old assumption. RedDepth keeps going where the evidence points.

See the evidence chain
03 VALIDATION

Earn the finding

Independent reproduction comes before a report draft. Confidence is useful; durable evidence is what ships.

Start from scope
SESSION TREE04 visible
Rreddepthcampaign ownerworking
Rreddepth-reconactive surface enumerationdone
Treddepth-testeridentity boundary / #024live
Vreddepth-validatorcandidate #007queued
Supervisor can inspect any child, at any time.
SSupervisorobserving campaign
Open by design

You stay in the room.

RedDepth lives in your OpenCode project. The primary agent owns the campaign, child sessions stay navigable, and every consequential action remains visible.

01Inspect the whySee the objective, scope reference, and decision at every step.
02Redirect the workChange strategy or priorities without losing campaign context.
03Stop with a checkpointPause safely. Resume from durable state, not a hidden worker.
Read the operating model
The evidence chain

Receipts for
every conclusion.

Raw captures land first. Summaries come second. The result is an investigation your team can inspect, reproduce, and trust.

01

Observe

Typed tools preserve the raw signal before interpretation.

02

Correlate

Hypotheses connect anomalies across identity, state, and surface.

03

Reproduce

An independent validator earns the right to call it a finding.

100%visible actions
0hidden schedulers
evidence-led depth
A different default

Depth is a posture,
not a setting.

RedDepth doesn’t stop at saturation, time, or an arbitrary worker limit. It stops when the surface is accounted for—or when you say stop.

Read the master brief
Ready when you are

Bring the scope.
We’ll bring the depth.

Open the RedDepth project in OpenCode. Confirm the authorized scope. Start the first visible turn.

Open the project No external dashboard. No background workers. Just the work, in the open.
Operator view replayed