Skip to main content

​
Model Requirements

This feature requires an advanced agentic model. It has been tested only with Claude Sonnet 3.5, 3.7, and 4.

​
How It Works

By default, Softcodes runs a built-in, invisible browser that:
  • Launches automatically when you ask to open a site
  • Takes screenshots of pages
  • Interacts with page elements (buttons, forms, etc.)
  • Runs quietly in the background
  • Requires no setup — everything works inside VS Code

​
Typical Workflow

  1. Ask Softcodes to open a site.
  2. The browser launches and returns a screenshot.
  3. Request follow-up actions: click, type, scroll, etc.
  4. Softcodes closes the browser when finished.
Examples:

​
Browser Actions

All interactions happen through the browser_action tool. After each action, you receive both a screenshot and logs so you can confirm results. Rules:
  • Sessions must start with launch and end with close.
  • Only one action is allowed per message.
  • While the browser is active, no other tools can run.
  • Wait for the screenshot/logs before sending the next action
Available actions:
ActionDescriptionExample Use
launchOpens a site in the browserStart a new session
clickClicks at specified coordinatesPress a button or link
typeEnters text into the active elementFill out forms, search boxes
scroll_downMoves one screen downView content below the fold
scroll_upMoves one screen upGo back to earlier content
closeEnds the sessionShut down the browser

​
Settings & Configuration

​
Default Setup

  • Browser tool: Enabled
  • Viewport size: Small Desktop (900×600)
  • Screenshot quality: 75%
  • Remote connection: Disabled

​
Accessing Settings

Open Settings → Browser / Computer Use.

​
Enable or Disable Browser Use

  • Master switch for Softcodes’s Puppeteer-powered browser.
  • Toggle the checkbox in Browser / Computer Use.

​
Viewport Size

  • Controls browser resolution.
  • Tradeoff: Larger viewports show more but increase token usage.
  • Options:
    • Large Desktop (1280×800)
    • Small Desktop (900×600) default
    • Tablet (768×1024)
    • Mobile (360×640)

​
Screenshot Quality

  • Defines WebP compression level.
  • Default: 75%
  • Ranges:
    • 40–50% → Lightweight, text-heavy pages
    • 60–70% → Balanced for most sites
    • 80%+ → Maximum clarity for detailed visuals

​
Remote Browser Connection

  • Lets Softcodes attach to a running Chrome instead of its built-in browser.
  • Advantages:
    • Works in DevContainers and remote setups
    • Keeps sessions logged in
    • Allows custom Chrome profiles/extensions
  • Requirements: Chrome must be launched with remote debugging enabled.
To enable:
  1. Check Use remote browser connection.
  2. Click Test Connection to confirm.

​
Common Use Cases

  • DevContainers: Connect containerized VS Code to a host Chrome instance.
  • Remote Development: Use your local Chrome while coding remotely.
  • Custom Profiles: Run sessions with specific extensions or settings.

​
Connecting to a Visible Chrome Window

Run Chrome with remote debugging flags: macOS 
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/chrome-debug \
--no-first-run
Windows 
"C:\Program Files\Google\Chrome\Application\chrome.exe" ^
--remote-debugging-port=9222 ^
--user-data-dir=C:\chrome-debug ^
--no-first-run
Linux 
google-chrome \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/chrome-debug \
--no-first-run