WROSECODE / AGENT CHAT
CHECKING?
WROSECODE / LIVE EXECUTION

Your machine.
One conversation away.

Send natural-language tasks to your WROSECODE Rust CLI on Kali. Events stream back here in real time.

● AGENT SESSION Waiting for command

Ready when you are.

Describe what you'd like WROSECODE to build, inspect, or investigate. Your commands run only if the server allows execution.

↵ Submit · Shift + Enter newline
CTF / EVIDENCE-DRIVEN AUTOMATION

Follow the evidence.
Find the flag.

Upload an authorized challenge artifact, launch the Rust `/ctf` workflow, and monitor live output. Flag patterns alone are never proof of a solve.

01 / CHALLENGE ARTIFACTAUTHORIZED ONLY
⬡

Drop a challenge file here

or click to browse · max 16 MiB · no automatic execution

No file selected
02 / LIVE INVESTIGATIONSTANDBY
ANALYSISWAITING
CANDIDATES0
VERIFIED FLAGS0*
// Agent output will appear here after the first run.
*Verification requires independent challenge authority confirmation. This bridge never labels a regex match as solved.
SESSIONS / TRACE

The work.
Accounted for.

Review your recent task and CTF executions. Each run is recorded independently.

EXECUTION HISTORY
MODEL / PROVIDER ROUTING

Your models.
One command center.

Provider profiles stay on Kali Linux. The website never displays stored API keys or tokens.

CONFIGURED WROSECODE PROVIDERS
Choose refresh to query the CLI.

Only provider names and masked CLI output are shown. Select provider/model in Agent chat. Backend respects your selection; it does not silently change providers.

DEVICE / PAIRING

Connect your
Kali CLI.

Pair this browser account to your running WROSECODE Rust server. The bearer token never leaves your Kali host.

CLI CONNECTION
Checking Rust server...
PAIR WITH CODE10-MIN EXPIRY

On Kali run: wrosecode bridge pair, then enter the 6-digit code below. Then start: wrosecode server --hostname 127.0.0.1 --port 4076

One-time use · bound to your login email
SECURITY / ACCESS MANAGEMENT

Access is
deliberate.

Review accounts and approve member access. Server execution remains owner-only unless explicitly enabled after configuring sandbox isolation.

ACCOUNT ACCESS