Start here

Set up your Hub

Zero to a working Hub in about ten minutes — all in your BlueRock cloud workspace, not on your laptop. You will connect your workspace, install the BlueRock plugin, create your Hub from the starter template, run the daily rhythm once, and open your dashboard, all before you build anything. You’ll barely touch the terminal. Already done a step? Skip it.

Three pieces work together, and they all live in the cloud. Your workspace is BlueRock’s secure cloud environment — your agents run there, off your machine. The plugin delivers your skills and agents (and is how you get new ones later). Your Hub — your own repo, made from the starter template — is where you and your agents actually work. The dashboard needs the plugin and your Hub: the plugin’s /bluerock:wrap-up writes the data, your Hub renders it. That is why you install the plugin and create your Hub. It works on day one; the curriculum makes it yours.

Before you start (skip what you have)

I need Cursor and a Claude subscription

Cursor — download from cursor.com and install it. This is the editor you connect to your workspace from.
A Claude subscription (Claude Pro or Max) — Claude Code runs inside your workspace and signs in with your own Claude account, the same login you use for claude.ai. No API key, no separate AI billing.

I need a GitHub account

Your Hub is saved in your own private GitHub repo — that is the habit we want you to build, so your work is versioned and yours. Go to github.com and click Sign up. Use your work email.
Pick a username: it becomes part of your repo URL, like github.com/<username>/<yourname>-hub.
Verify your email when GitHub sends the link.

Connect your workspace

You get a cloud workspace — a secure scaffold our team keeps ready for you. You connect Cursor to it once, then work inside it like any other project. The connect steps live in your BlueRock console, on your workspace’s Connect tab:

Install BlueRock Connector — search “BlueRock Connector” in Cursor’s extensions, or use the Add to Cursor button on the console’s Connect tab.
Point it at your workspace — copy the bootstrap URL from the console and paste it when the Connector asks. It pins your workspace so Cursor only ever connects to the real one.
Sign in to BlueRock — the same BlueRock account you used for the console. This gets you into the workspace.
Open your workspace from the Connector. This puts you inside the cloud environment, where everything else happens.

Then install Claude Code in your workspace:

Your workspace starts bare, so Claude Code isn’t there yet — you install it once, and because your workspace is saved it stays installed. Open a terminal in the workspace (Ctrl+`, the key above Tab) and paste this one line:

in the workspace terminal

curl -fsSL https://claude.ai/install.sh | bash

When it finishes, close and reopen the terminal (or run export PATH="$HOME/.local/bin:$PATH") so the claude command is found. Then start Claude Code by typing claude in the terminal, or open the Claude Code panel in Cursor.

Sign in to Claude Code with your own Claude account (the same login you use for claude.ai). This powers Claude Code inside the workspace.

Two sign-ins, and they do different jobs: your BlueRock account gets you into the workspace; your Claude account powers Claude Code once you’re there.

Cursor is connected to your workspace, claude runs in the terminal (no “command not found”), and Claude Code is signed in and ready.

Install the BlueRock plugin

The plugin delivers your working skills and agents — /bluerock:onboard, the daily-brew and scribe agents, /bluerock:today, /bluerock:meeting-recap, /bluerock:wrap-up, plus the Account Research team (/bluerock:research). Installing it now gives you the working set; later, it’s also how new skills and agents reach you, without rebuilding anything. In the Claude Code panel, run these two lines:

in Claude Code

/plugin marketplace add bluerock-io/claude-plugins
/plugin install bluerock@bluerock

Then run /bluerock:check. It tells you, in plain English, whether everything is ready.

You rarely type the full command. Every BlueRock skill also fires from plain language — say “wrap up my session” and Claude runs /bluerock:wrap-up for you. The /bluerock: form is the explicit path when you want it; your words are the everyday one.

/bluerock:check reports green, and the BlueRock skills show up when you type / in Claude Code.

Create your Hub from the starter template

The starter project is a template — your starting point, not something you edit in place. You make your own copy (that copy is your Hub), then clone it into your workspace. It comes seeded with a standing brief, a notes convention, and the dashboard; the skills and agents come from the plugin you just installed, and the curriculum shows you each one as you go.

First, make your copy on GitHub:

Open bluerock-io/hub-starter (signed in to GitHub).
Click “Use this template” (top right) → “Create a new repository.”
Repository name: <yourname>-hub (like maria-hub). Visibility: Private — your notes and profile live here.
Click “Create repository,” then the green “Code” button and copy the HTTPS URL.

Then clone it into your workspace:

In Cursor (connected to your workspace), press Cmd+Shift+P / Ctrl+Shift+P and run “Git: Clone.”
Paste your repo’s URL (yours, not the template) and pick a folder in the workspace.
First time only: a browser tab opens so your workspace can reach your private repo. Click “Authorize” and return.
When the clone finishes, click “Open Cloned Repository.”

If your Hub doesn’t open on its own: over a remote connection Cursor sometimes lands at the top of your workspace instead of inside your Hub. Open it yourself — press Cmd+Shift+P / Ctrl+Shift+P, run “File: Open Folder,” and pick the folder you just cloned (or in the terminal, cd into it). Either way you’re covered — the BlueRock skills find your Hub wherever you run them, so nothing lands in the wrong place. Opening the folder just gives you the file tree and the welcome greeting.

Your Hub is open in the workspace — the file tree shows the seeded files (CLAUDE.md, notes/, examples/, design/), and the status bar shows main.

Run the rhythm once

You now have everything to run the loop end to end, without building anything. In the Claude Code panel, in your Hub:

Capture something: say capture: had a call with Alex about the Q3 renewal (or /bluerock:capture …). It files a note for you.
Get a brief: say run daily-brew. It reads your notes and returns a morning brief, and seeds today.md.
Check your list: say show my priorities (or /bluerock:today) for your living list.
Close the session: say wrap up my session (or /bluerock:wrap-up). It logs what the session did, refreshes your dashboard data, and offers to commit and push to your GitHub repo. Say yes — that is how your work gets saved.

How saving works, for when you do it yourself: the Source Control panel (Ctrl+Shift+G) is where you Commit (save a snapshot) and Sync Changes (push it to your GitHub repo). /bluerock:wrap-up does both for you, but this is the manual path if you ever need it.

A notes/<date>.md and a today.md now exist in your file tree, and /bluerock:wrap-up reported what it saved.

Open your dashboard

Just say open my dashboard. Because your Hub lives in the cloud workspace, Claude Code starts a quick preview server and hands you a link — click it (or the port notification Cursor shows) and your dashboard opens in your browser. It reads the data /bluerock:wrap-up just wrote and shows what your agents did this session.

A note on the numbers: your dashboard is built from your own sessions, derived from what /bluerock:wrap-up records — not from a sensor or a server watching you. What you see is yours.

The dashboard opens in your browser and shows real numbers from your session. That glow is the point: a working system with a dashboard of its own activity, nothing authored yet.

Coming back later

Close Cursor and come back tomorrow? Your workspace and your Hub are saved. To pick up where you left off: reopen Cursor, use BlueRock Connector to open your workspace, and your project is right there. No re-cloning, no re-setup. (You may be asked to sign in again — that is normal.)

What’s next

That is the day-one promise. Everything from here makes it yours, starting with teaching your Hub who you are and how you write. Begin the curriculum with the anatomy of an agent, then prime your Hub in Module 2.

Start Module 1

If something fails

Troubleshooting

Symptom	Fix
claude: command not found	Claude Code either didn't finish installing, or the terminal hasn't picked it up yet. Re-run the install line (curl -fsSL https://claude.ai/install.sh \| bash), then close and reopen the terminal — or run export PATH="$HOME/.local/bin:$PATH" — and try claude again.
I don't see BlueRock Connector in the marketplace	Search for "BlueRock" (one word). If it still doesn't appear, install links live in your BlueRock console on the Connect tab — use the Add to Cursor button there.
The workspace won't open, or the Connector can't reach it	Go back to your console, open your workspace, and re-copy the bootstrap URL — it pins your workspace so the Connector connects to the right one. Paste it when the Connector prompts.
The /plugin command does nothing or is not found	Make sure you are in Claude Code (the panel inside Cursor, connected to your workspace), not a plain chat. Then re-run the marketplace add and install lines exactly.
No "Use this template" button on the repo page	You are either not signed in to GitHub, or you are looking at your own copy instead of the template. Sign in, then open the template URL again.
Git: Clone asks me to authorize GitHub	First time only — a browser tab opens so your workspace can reach your private repo. Click Authorize and return. If it fails, open the Source Control panel (Ctrl+Shift+G) and retry.
The dashboard link doesn't open, or the page is empty	Run /bluerock:wrap-up first — it writes design/dashboard-data.js, which the dashboard reads. Then say "open my dashboard" again; click the forwarded link (or Cursor's port notification).
A skill says it can't find my Hub, or my files landed in the wrong place	Your session started outside your Hub — common over a remote connection, where Cursor opens at the top of your workspace with your Hub one folder down. The skills look for it automatically, but to be sure, open the Hub folder: Cmd+Shift+P / Ctrl+Shift+P → "File: Open Folder" → pick the folder you cloned (or cd into it in the terminal). Then run the skill again.
I closed Cursor and lost my work	You didn't. Your workspace and your Hub are saved. Reopen Cursor, use BlueRock Connector to open your workspace, and everything is where you left it.

Fallback for the git identity dialog only — most people never need it. Aside from installing Claude Code during setup, this is the only other terminal command you’ll see. Open the terminal in your workspace (Ctrl+`), paste these two lines with your real name and email, then close it.

one-time git identity (fallback)

git config --global user.name "Your Name"
git config --global user.email "you@yourcompany.com"

Still stuck? Send Linda a screenshot of where you are.