OxoSecurityOPERATOR
/

The workspace for the next generation of security engineers.

AI Workspace
for Security Engineers

Let the Agent work across browser, requests and code in one workspace—so you switch tools less and focus on verifying vulnerabilities.

See it in action
Codex SDKSpacesLLM Security Scan
SECURITY WORK. ONE WORKSPACE.OXO OPERATOR
BrowserHTTP trafficRequestsFiles & codeTerminalSecuritySpaces

Less handoff. More investigation.

Your tools already do important work. Oxo Operator connects the work between them—so the context travels with the task.

ACT

An Agent that does the work.

Reproduce a browser flow, inspect a request, search the project and run a check. Direct the investigation from one conversation.

CONNECT

The request stays with the code.

Carry selected HTTP context into a bounded search for candidate routes and handlers. Keep the original and each request revision.

REMEMBER

The next task has a starting point.

Keep selected project sources in Spaces. Reuse original evidence with source versions and verifiable locations.

See what the workspace can do.

From a browser flow to a saved request.

Operate the browser, inspect HTTP traffic and save a separate request revision.

Find the code behind the question.

Search your local project from a selected request. Inspect candidate code in context.

Put your security tools to work.

Call security tools in the conversation, run checks and review their output.

Pick up where the last task left off.

Keep original project material, its version and its source location in Spaces.

Plugins and connection boundaries+
GitHub

Repositories, issues and pull requests.Read repositories, issues and PRs · issue creation needs approval.

Jira

Work items and project context.Read work items · creating or updating them needs approval.

Local Git

Status, diffs, history and branches.Read-only tools · work on this machine.

Semgrep

Code security in your workspace.Runs locally · no connected account required.

Trivy

Dependencies, secrets and configuration.Runs locally · no connected account required.

OWASP ZAP

Alerts, history and scan status.Read existing data · spider and active scans need approval.

Give it a question. Follow the work.

A connected workflow, with the final judgment still yours.

OperatorEXAMPLE PROJECT
Conversationsession-boundary
You

Inspect the sign-in flow, retain the request and find the related local code.

Oxo Operator

The relevant browser action stays attached to this investigation.

Opening the application in Browser
Browser01 / 05
https://session-lab.local/login
EXAMPLE · SCOPED TEST APP

Sign-in flow

No credentials or network requests are submitted.

Agent
Authorized project scope

CONTROL STAYS WITH YOU

Delegate the work. Keep the judgment.

The project, selected runtime and permission profile define the operating boundary. Inspect activity and decide how much autonomy fits the task.

01Project scope+

Start from an authorized target and the relevant local repository.

02Runtime-aware approvals+

Available actions and approval behavior depend on the configured runtime and policy.

03Reviewable results+

A model’s confidence is not proof. Verify reproduction, impact and exploitability.

04 / RESEARCH

The thinking behind the workspace.

Explore research
Security engineerobjective · authorised scope
Oxo Operatoragent loop · Codex SDK

Workspace context

  • Browserhttps://session-lab.local/login
  • TrafficGET200/loginPOST200/api/session
  • RequestPOST /api/sessionrevision 03 · retained
  • Files / codereturn sessionService.issue(identity)
  • Terminalpnpm vitest run session-boundary.test.tsexit 0
  • Spacesoriginals · source versions · navigation
  • Evidencetransaction #142 · revision 03 · exit 0
Application, HTTP requests, project files and terminal work share task context and records a reviewer can reopen.
Updated October 28, 2026 · 14 min read

Building an AI-Native Security Workspace

A security investigation spans a browser, an HTTP history, a source tree, a terminal and a tracker. This note examines what it costs when the engineer is the only thing connecting them — and what changes when the unit of work becomes a task-bound workspace.

Read the note

Selected space material

  • documents
  • source files
  • notes
Originals + local indexSave material, then check processing status

Source

session-boundary.md

Version

v3 · s_7f3a

Location

lines 12–16
Navigate → read originalAgents.md / search → bounded source evidence
Search and navigation lead to relevant original passages. A source version and location let the engineer reopen the context behind a conclusion.
Updated October 28, 2026 · 8 min read

Grounding Workspace Knowledge in Original Sources

Spaces connects project material to its original text, version and location. Search, navigation and references help agents find context and engineers check the basis of a conclusion.

Read the note
Discover
  1. Explore the targethttps://session-lab.local/login
  2. Inspect the requestPOST200/api/session
  3. Locate candidate codesrc/server/routes/session.ts:42
Operate
  1. Select a toolSemgrep · static analysis, runs locally
  2. Run local rulesSemgrep · bundled rule pack
  3. Read the resultrule matches · needs validation
Verify
  1. Verifyexit 0 · bound to revision 03
  2. Collect evidencetransaction #142 · revision 03
  3. Prepare a findingAuthentication boundary · needs review

One workspace context

  • browser
  • request
  • code
  • tool output
  • evidence

The request the agent captured in step two is the request it correlates in step six; the command it ran in step five is the receipt the finding cites.

Before: nine steps across five tools, each handoff a manual copy.

The workflow a security engineer already follows, in three stages — each step writing into the same record instead of into a different application.
Updated October 28, 2026 · 15 min read

AI-Assisted Red Teaming: From a Security Task to a Continuous Workflow

Red teaming a real application is mostly mechanical: the same request, the same handler and the same command, carried between tools by hand. This note asks how much of that an agent can perform, and where the engineer's judgement has to stay.

Read the note

START WITH A PROJECT YOU KNOW

Your next investigation starts here.

01

Connect your model

Use your own Responses-compatible model service.

02

Choose the workspace

Attach the relevant project and define the authorized scope.

03

Ask a concrete question

Start small. Inspect the work and verify the result.

Download Oxo Operator.

A desktop workspace for security engineers.

Current releasev0.1.18Windows · x64

Preview installer · not Windows code signed
Bring your own model service.

Before you start, read the use agreement and runtime risks.

What happens to my project data?+

The workspace runs locally. When you use a remote model, selected context and tool output may be sent to your configured provider. Review its data policy before working with sensitive projects.

Do I need to replace my existing tools?+

Oxo Operator provides its own security work surfaces and can use configured tools through the terminal, plugins and MCP. Integration depends on the tool and connection; it does not require a wholesale migration.