Context

This page shows where bproxy sits in its surroundings. The diagram draws the system as a single box and surrounds it with the people who use it and the other systems it talks to. How bproxy works on the inside — the parts it is built from, the technologies, the run-time setup — belongs to the other pages linked at the bottom.

---
title: bproxy — System Context
---
flowchart TB
  Agent["Code Agent
[External Software System]
Automates tasks via bproxy commands"]
  Operator(["Operator
[Person]
Owns the browser session and runs bproxy"])
  Bproxy["bproxy
[Software System]
Localhost control surface around a user-owned browser"]
  Browser["User Browser / Chrome Profile
[External Software System]"]
  Site["Target Web Sites
[External Software System]"]

  Agent -- "issues commands to" --> Bproxy
  Operator -- "operates" --> Bproxy
  Bproxy -- "hands off to" --> Operator
  Bproxy -- "controls browser session" --> Browser
  Operator -. "«owns»" .-> Browser
  Browser -- "browses" --> Site

  Site ~~~ Legend

  subgraph Legend["Legend"]
    direction LR
    LP(["Person"]):::person
    LS["System under
design"]:::system
    LE["External
system"]:::external
    LP ~~~ LS ~~~ LE
  end

  classDef person fill:#08427b,color:#fff,stroke:#052e56;
  classDef system fill:#1168bd,color:#fff,stroke:#0b4884;
  classDef external fill:#999999,color:#fff,stroke:#6b6b6b;
  class Operator person;
  class Bproxy system;
  class Agent,Browser,Site external;

Figure 1. System context for bproxy — the people and external systems that interact with the tool, and the broad nature of each relationship. Dashed edges denote static ownership rather than active interaction.

What this picture tells you

bproxy is not a browser of its own. It runs on the operator’s machine and drives an existing Chrome session. The code agent never touches a web page directly — every action goes through bproxy, which translates it into work inside the real browser. The agent’s window into the web is always the operator’s browser, never a separate automated context.

The operator owns everything on the browser side: the Chrome profile, the cookies, the saved logins, the browser fingerprint. They also stay in the loop while bproxy runs — starting the service, pairing the extension when it first connects, and stepping in whenever bproxy asks for human help. Ownership and supervision are part of the design, not hidden behind automation.

Context

What this picture tells you

See also