What is the Gateway?
The Gateway is a local service that runs on your machine, connecting CORE to your development environment. It enables CORE to automate browsers, spawn coding agents, and execute shell commands - all triggered remotely from any channel like WhatsApp, the web dashboard, or another AI agent. Think of it as the bridge between CORE’s cloud intelligence and your local machine’s capabilities.Why Use It?
Browser Automation
Control headless or headed browsers with persistent profiles for authentication
Coding Agents
Spawn Claude Code or other coding agents on your machine from anywhere
Shell Commands
Execute commands on your machine with configurable allow/deny patterns
How It Works
Gateway Commands
| Command | Description |
|---|---|
corebrain gateway start | Install and start the gateway service |
corebrain gateway stop | Stop and remove the gateway service |
corebrain gateway restart | Restart the gateway service |
corebrain gateway status | Check gateway status |
corebrain gateway config | Configure gateway settings |
Capabilities
The gateway exposes three main capabilities to CORE:Browser
Automate browsers with persistent profiles
Coding
Spawn and manage coding agent sessions
Exec
Execute shell commands with security controls
Use Cases
Remote development: You’re on your phone, a bug comes in. Message CORE on WhatsApp: “Fix the auth timeout issue in the API.” CORE spins up Claude Code on your machine, pulls context from memory, and starts working. Automated testing: CORE opens a browser, logs into your staging environment, runs through a test flow, takes screenshots, and reports results - all from a scheduled reminder. Daily workflows: “Every morning at 9am, check my GitHub notifications and summarize what needs attention.” CORE runs commands on your machine to gather the data.Security
The gateway runs locally on your machine with configurable security controls:- Browser profiles are stored locally and persist authentication
- Exec commands can be restricted with allow/deny patterns
- Coding agents run in isolated sessions with full audit trails