oc-as

Launch an isolated headed Chromium browser in a per-project Docker container.

Updated Mar 1, 2026

Search Tags:#docker #web-automation #browser-automation #project-scoped #oc-as #headed-chromium

Ready to run

npx skills add https://github.com/hve4638/hve-cc-marketplace --skill oc-as

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oc-as
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/oc-browser/skills/oc-as
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill oc-as

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the setup and management of an isolated, headed Chromium browser instance per project, removing the need to manually wire up containers and display options for automated web tasks.

Core Features & Use Cases

Per-project isolation with automatic container lifecycle on first use and explicit removal via oc-rm.
Multiple display modes (headless, host X, and noVNC) for flexible automation and testing.
A sibling oc browser command enables container-free operation inside a compatible environment.

Quick Start

Launch an isolated browser container and begin browsing or automating tasks.

Frequently Asked Questions about oc-as

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run an isolated headed Chromium browser in Docker for web automation?▼

To run an isolated headed Chromium browser in Docker, this Skill automatically provisions a per-project container with lifecycle management, supporting headless, host X, and noVNC display modes for flexible web automation tasks.

What's the best way to automate web tasks across multiple projects without container conflicts?▼

Automating web tasks across projects without conflicts requires per-project isolation, which this Skill provides by spinning up dedicated Docker containers for each project and managing their lifecycle through explicit removal via oc-rm.

Can I use noVNC or host X display modes for headed browser automation in Docker?▼

Yes, you can use noVNC or host X display modes for headed browser automation. The Skill supports multiple display options including headless, host X, and noVNC to accommodate different testing and interaction requirements.

Do I need Docker to run isolated Chromium instances for scraping dynamic pages?▼

Yes, you need Docker to run isolated Chromium instances for scraping dynamic pages. The Skill relies on Docker and OpenClaw tooling to drive the headed browser, though a sibling oc browser command exists for containerless operation in compatible environments.

How do I remove an isolated browser container after completing project-scoped automation?▼

To remove an isolated browser container after project-scoped automation, you use the oc-rm command, which provides explicit lifecycle management to safely tear down the per-project Docker container once your web tasks are finished.

What are the limitations of using a container-scoped browser for automated site interactions?▼

Limitations of using a container-scoped browser include the dependency on Docker and OpenClaw tooling for operation, and the need for explicit lifecycle management, although a sibling oc browser command offers a containerless alternative within compatible environments.