Add Claude Code project configuration with chrome-host MCP bridge for browser automation#717
Merged
Merged
Conversation
bedrich-schindler
temporarily deployed
to
pr-preview/pr-717
June 30, 2026 10:15 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
|
adamkudrna
approved these changes
Jul 1, 2026
adamkudrna
left a comment
adamkudrna
left a comment
Member
There was a problem hiding this comment.
So we are dumping ourselves into markdowns, aren't we 🙂.
Although I went through the chrome-host stuff and "understand" it, my official statement is "I have no idea what's going on".
I'm really looking forward to get this working.
mbohal
approved these changes
Jul 2, 2026
mbohal
left a comment
mbohal
left a comment
Contributor
There was a problem hiding this comment.
I did not read it throughly, but I confirm it runs on Linux.
bedrich-schindler
force-pushed
the
task/claude-integration
branch
from
July 4, 2026 12:09
a82a575 to
a4221b6
Compare
bedrich-schindler
temporarily deployed
to
pr-preview/pr-717
July 4, 2026 12:10 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
… browser automation Introduce CLAUDE.md and a .claude/ directory so Claude Code works from the project's documented conventions instead of guessing. * CLAUDE.md — entry doc: project overview, the devcontainer command workflow, and an index of rules, agents and the `/commit` skill. * .claude/rules/ — always-on rules (code, git, safety-guards) and path-scoped rules (frontend, styling, testing, docs) carrying the project conventions. * .claude/skills/commit/ — the `/commit` skill for committing per project rules. * .claude/agents/code-reviewer.md — a repo-tailored review agent. * .claude/settings.json — scoped command permissions and enables the `chrome-host` MCP server (plus the GitHub and Context7 plugins). Speaking of chrome-host MCP bridge: Add tooling that lets an MCP-capable assistant in the `devcontainer` drive Chrome running on the host via `chrome-devtools-mcp` over the Chrome DevTools Protocol. Because the container can only reach the host through `host.docker.internal` and Chrome's DevTools endpoint rejects non-IP `Host` headers, a small loopback proxy (`cdp_proxy.py`) runs inside the `node` container and forwards to host Chrome, so the `Host` Chrome sees stays `127.0.0.1`. Includes the host launcher (`start-host-chrome.sh`, throwaway profile opening the docs site), the in-container launcher and entry scripts, native-Docker host-gateway setup, MCP registration for Claude/Copilot (`.mcp.json`) and OpenCode (`opencode.json`), and documentation.
bedrich-schindler
force-pushed
the
task/claude-integration
branch
from
July 4, 2026 12:28
a4221b6 to
bb0da69
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce CLAUDE.md and a .claude/ directory so Claude Code works from the project's documented conventions instead of guessing.
/commitskill./commitskill for committing per project rules.chrome-hostMCP server (plus the GitHub and Context7 plugins).Speaking of chrome-host MCP bridge:
Add tooling that lets an MCP-capable assistant in the
devcontainerdrive Chrome running on the host viachrome-devtools-mcpover the Chrome DevTools Protocol.Because the container can only reach the host through
host.docker.internaland Chrome's DevTools endpoint rejects non-IPHostheaders, a small loopback proxy (cdp_proxy.py) runs inside thenodecontainer and forwards to host Chrome, so theHostChrome sees stays127.0.0.1.Includes the host launcher (
start-host-chrome.sh, throwaway profile opening the docs site), the in-container launcher and entry scripts, native-Docker host-gateway setup, MCP registration for Claude/Copilot (.mcp.json) and OpenCode (opencode.json), and documentation.