Skip to content

question: Support browser automation workflows via Chrome attach or MCP integration #957

@walker1211

Description

@walker1211

Topic

None

What do you need help with?

Would you consider adding browser automation support to CCS, either natively or via first-class MCP
integration?

A capability similar in spirit to claude-in-chrome would be very useful for workflows where
agents need to interact with real web pages: reproducing UI issues, validating flows, extracting
page content, and working with authenticated web apps.

CCS already does a great job managing providers/runtimes/profiles, so browser-capable workflows
feel like a natural next step. I'm not strongly attached to a specific implementation approach —
native support or smoother MCP integration would both be great.

Would this be considered in scope?

Context

No response

CCS version

No response

Operating system

None

Before submitting

  • I checked the docs and existing issues first.
  • This is not a private security disclosure.

Metadata

Metadata

Assignees

Labels

area:cli-runtimeCLI runtime commands, execution flow, and core target behaviorquestionFurther information is requested

Projects

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions