Build and run a Dockerized IronClaw web gateway test environment with Chrome MCP browser automation.
npx skills add https://github.com/nearai/ironclaw --skill local-test-nearai
Please help me install this Agent Skill. Skill: local-test Source: https://github.com/nearai/ironclaw/tree/main/skills/local-test Command: npx skills add https://github.com/nearai/ironclaw --skill local-test-nearai
It removes the guesswork of how your IronClaw web gateway changes will behave by letting you build and run a dedicated local Docker test environment with browser-driven verification.
Build the test image and start the web gateway container, then open http://localhost:3003/?token=test in your browser.
High-intent search queries and answers about installing and using this skill.
Local testing for web gateway changes requires building a Dockerized test environment with Dockerfile.test, configuring environment variables, launching the container on a specified port, and executing a Chrome MCP workflow to verify UI loading and gateway connectivity.
A Chrome MCP browser automation workflow for UI smoke tests opens web pages programmatically, verifies connectivity, checks UI state like tabs and connection indicators, captures screenshots, and runs page-level JavaScript checks to validate interactions across desktop and mobile viewports.
Yes, you can test UI flows against different LLM backends. The test environment supports configuring NEAR AI, OpenAI, Anthropic, or a dummy mode, allowing you to exercise the UI and validate gateway routines across various providers or use dummy mode for fast UI validation.
No, you do not need PostgreSQL to build and run the local test environment. The Docker test build operates using a libsql-only configuration, removing the PostgreSQL dependency for reproducible Docker test runs and gateway validation.
The best way to validate web gateway changes across desktop and mobile viewports is using browser automation to capture screenshots and run page-level JavaScript checks. This reproducible Docker test environment drives a Chrome workflow to smoke-test interactions across different viewport sizes.
Your local web gateway test environment needs environment variables to configure the LLM backend, set the gateway port, and establish authentication tokens. Proper configuration ensures the Dockerized test environment builds correctly and the Chrome MCP workflow can verify connectivity.
caelum0xBuild and run IronClaw web gateway tests locally with Docker and Chrome MCP automation.
wordshepherdCapture desktop, mobile, and dark mode screenshots while checking console and network errors.
JustinWangJPAutomate browser debugging and web page manipulation via Chrome DevTools MCP.
hainamchungExecute coding tasks immediately by bypassing the planning phase.
