Original Pages

Vol. 01 · Field notes, not blog filler

OriginalPages

Practical setup guides for Cursor, Claude, Grok Bot, and related AI coding tools. We write the pages you actually need after an update: Desktop versus CLI versus Cloud Agents, MCP that stays green, and the Windows paths that keep getting mixed up.

Checked daily

What changed

Official Cursor and Claude Code versions, plus Grok Bot marketplace listings, republished once a day from first-party sources.

  • Cursorv3.19.19
  • Claude Codev2.1.266
  • Grok Bot marketplacedr eggbot · Overheard · Tradbot

Full live desk →

First time here?

Start with install and a first useful change. Jump to the harder pages only when you hit the problem they name.

  • Getting started with CursorInstall on Mac, Windows, or Linux, then Tab, Inline edit, Agent’s four modes, context with @, and how to undo with Checkpoints.
  • Getting started with Claude CodeNative install on Mac, Linux, WSL, and Windows, first session in a real project, a read-first prompt, then one small change before you write CLAUDE.md.
  • Grok Bot: info, FAQ, and examplesNamed teammates on a persistent cloud computer — not the Grok model in the picker. Marketplace listings, how to publish a Bot, FAQ, and starter prompts that stop at review.

What these pages are for

Original Pages is a small, independent site of free, first-hand guides for Cursor, Claude Code, and Grok Bot — for people already using the tools who have hit something the official docs do not fully explain: a red MCP server, a rules file that stopped working, a Cloud Agent that cannot see a file you know is there, or a Grok Bot that is not the model in the picker.

Most AI coding posts repeat the same “install the app, add a rule, enable MCP” loop. Original Pages starts at the install path when that path is messy, then stays with you after: which surface you are actually on, where the files live, and what still works after Cursor ships an update.

Every guide is checked against the current official Cursor and Claude Code documentation before it is written, not recalled from memory, and is written for two readers at once: a short version at the top for people who already know the tool and arrived here mid-problem, and a plain-English explanation underneath for people meeting the thing for the first time. Where the official documentation is silent, ambiguous, or contradicts a widely-repeated claim, the pages say so rather than inventing an answer.

Cursor

Claude Code

  • CLAUDE.md that actually worksWhere Claude Code looks for memory files, why they concatenate rather than override, how long yours should be, and how to check what actually loaded.

Where they overlap

  • Using Claude with CursorRules, MCP and settings are configured separately in each tool — except CLAUDE.md, which both of them read. What each one owns.
  • CLAUDE.md vs .cursor/rules: which one winsCursor reads both files. Claude Code never reads .cursor/rules. The relationship is asymmetric, documented, and not what most people assume.
  • AWS integration with Cursor, Claude, and GrokCursor’s Bedrock BYOK routing, Claude Code’s first-class Bedrock provider, the three separate things called “Grok”, and the awslabs MCP servers — what actually runs on your AWS account.