Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Once the Gateway is running on your machine, you can kick off a Claude Code session from your phone via WhatsApp or Slack. CORE routes the message through the Gateway, spawns the session, and reports back when it’s done.

​
Connect the Gateway to your instance

The CORE CLI connects to CORE Cloud by default. For a self-hosted instance, point it at your own deployment when logging in: 
npm install -g @redplanethq/corebrain
corebrain login
# When prompted for instance URL, enter your APP_ORIGIN (e.g. https://your-domain.com)
# Leave blank for localhost
Make sure APP_ORIGIN and LOGIN_ORIGIN are set correctly in your .env: see Docker setup.

​
Setup

1

Install the Claude Code Plugin (Optional but Recommended)

The CORE Brain plugin gives Claude Code persistent memory across sessions: your preferences, past decisions, and project context load automatically every time.Open Claude Code and run:
/plugin marketplace add redplanethq/core
/plugin install core_brain
Then restart Claude Code and authenticate:
/mcp
# Select core_brain and authenticate via browser
See the full Claude Code plugin guide for details.
2

Configure and Start the Gateway

The Gateway is a local service that runs on your machine. It’s what allows CORE’s cloud agent to reach your machine and spawn Claude Code sessions remotely.
corebrain gateway config
corebrain gateway start
Once the gateway is running, CORE can communicate with your machine from anywhere.

​
Starting a Session from WhatsApp

Once the gateway is running, message CORE on WhatsApp to start a session. Always include the repo path and branch so CORE knows where to work. Example message:
start a claude code session repo: ~/Github/core branch: fix/auth-timeout task: fix the auth timeout bug in the api
CORE will create the branch, launch Claude Code, and keep you updated as it works.

​
Tips for remote sessions

  • Always include the repo path: e.g., ~/Github/core or /Users/you/projects/myapp
  • Always include the branch: CORE will create and checkout the branch from main
  • Be specific with the task: the more precise, the better the output

​
Sample Query to Try First

Not sure what to start with? Try asking CORE to summarize the codebase:
start a claude code session repo: ~/Github/core branch: explore/codebase-overview task: explain this codebase to me in a brief summary: what it does, key directories, and main entry points
CORE will start the session and send you a summary when it’s done.

​
What Happens Next

CORE reports progress in milestones:
  • started: session created and agent launched
  • checkpoint(s): e.g., “tests passing”, “fix landed”, “PR ready”
  • complete: summary of changes, files modified, and next action for you
You can also check in anytime:
status of the coding session?