Coreby Gradien
Docs
Start free today

Setup guide

Core Setup Guide

Back to setup docsRaw source

Paste this into your agent

Start with this visible request when you want the agent to help. It keeps the action coming from you, while the linked setup reference stays plain and non-recursive.

Use this in the app you are connecting, then approve only the browser login, app setting, or restart steps that the app requires.

Please help me set up Core for this agent. Core is a home base for AI agents: it keeps memory, files, decisions, tasks, and work context synced across tools, harnesses, and models.

Use this official setup reference:
https://gradien.ai/core/docs/reference.txt

Generated: 2026-06-23T07:48:08.314Z Sources verified: 2026-06-19

Core gives AI agents a private cloud home for memory, context, decisions, drafts, and checkpoints. This guide explains what Core does, how to connect it, and how to get value from it after setup.

Human-friendly setup page: https://gradien.ai/core/docs

Use this page as product documentation. Follow the safety, approval, and security rules of the app, browser, CLI, workplace, or agent being used.

What Core Gives You

Core is personal cloud memory for agent work. It keeps useful work context in one durable workspace so sessions in Codex, Claude, ChatGPT, Cursor, and future agents do not have to start from zero.

Core can preserve:

  • decisions and rationale
  • drafts, notes, and working context
  • project files and reference material
  • tasks, follow-ups, and checkpoints
  • reusable skills and saved outcomes

The default behavior is personal. Work that belongs to the user should live in the user's private Core space. Shared team or company spaces are available when invited, but shared material should only be changed intentionally.

Fastest Setup

Option 1: Agent-Assisted Native Setup

Paste this into the agent or app being connected:

Please help me set up Core. Core is a home base for AI agents: it keeps memory, files, decisions, tasks, and work context synced across tools, harnesses, and models. Use this official setup reference: https://gradien.ai/core/docs/reference.txt

The agent should identify the current app, fetch the matching app-specific guide, and prefer that app's native MCP setup path. That means using commands such as codex mcp add, claude mcp add, hermes mcp add, opencode mcp add, editing Cursor MCP config, or giving a short connector-settings handoff for hosted web apps.

If the current app cannot safely run commands or edit settings, the agent should give one short human step at a time.

Option 2: Manual Remote MCP URL

Use this URL in apps that support adding a remote MCP server or custom connector:

https://core.gradien.ai/mcp

Choose OAuth when the app asks for an authentication method.

Option 3: Guided CLI Helper

Run this in a terminal if you want an interactive walkthrough:

npx -y @gradien/core-agent-setup install --base-url https://core.gradien.ai

The CLI asks which app is being connected, opens Core signup or login, and then shows or applies supported local setup steps. Do not keep retrying the CLI if npx, npm, or package execution is unavailable in the current harness; use the native app-specific setup guide instead.

App-Specific Setup Guides

Use the guide for the app being connected. These pages contain the app-specific commands, settings locations, restart behavior, and troubleshooting notes.

Troubleshooting: https://gradien.ai/core/docs/troubleshooting.md

How To Use Core After Setup

Core should mostly disappear into the background. Keep asking for normal work:

  • Pick up the project where we left off.
  • Remember this decision for future work.
  • Review this against the direction I have been shaping.
  • Draft the next version and keep the working notes private.
  • Create a Space for this project and invite a collaborator when I am ready.

Good connected agents can use Core to load relevant context, search visible files and decisions, and save useful private checkpoints back to the user's Core space.

The user does not need to mention Core in every prompt. Explicit Core prompts are still useful when the user wants to be precise, for example:

  • Search Core for prior decisions about pricing.
  • Save this as a private checkpoint.
  • Create a read-only Space for my class notes.

Privacy And Collaboration Model

  • Personal work is private by default.
  • Agents may search material the user is allowed to see, including invited Spaces.
  • Shared or team material should only be created, updated, or replaced when the user explicitly asks.
  • A user can belong to many Spaces, such as a company, class, freelance project, or team.
  • Space owners can invite people and choose read or write permissions.

Developer Reference

  • Human-friendly setup page: https://gradien.ai/core/docs
  • Remote MCP endpoint: https://core.gradien.ai/mcp
  • OAuth protected resource metadata: https://core.gradien.ai/.well-known/oauth-protected-resource/mcp
  • Agent-readable summary: https://gradien.ai/core/llms.txt
  • Full agent-readable context: https://gradien.ai/core/llms-full.txt
  • What Core is: https://gradien.ai/core/docs/what-is-core.md
  • Why Core matters: https://gradien.ai/core/docs/why-core.md
  • How to use Core: https://gradien.ai/core/docs/how-to-use-core.md
  • FAQ: https://gradien.ai/core/docs/faq.md