Coreby Gradien

Reference

How To Use Core

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

Core should mostly disappear after setup. Keep asking for normal work. A connected agent can use Core automatically when visible context, prior decisions, files, tasks, or saved private outcomes would help.

Good user prompts after setup are just normal work prompts:

  • Update the landing page copy.
  • Find what we decided about pricing.
  • Continue the onboarding work from last time.
  • Review this PR against our product direction.

The Core loop is meant to happen in the background:

  1. Use core_start_work when current visible Core context would improve the work.
  2. Use core_search and core_read to pull exact visible context.
  3. Do the work in the current agent or harness.
  4. Save ambient artifacts, drafts, and checkpoints to /private by default.
  5. Use /teams/<team-slug> or /shared only when the user explicitly asks to upload, publish, or update team/company-visible material.
  6. Use core_record_work before ending meaningful work so decisions, files changed, tests run, risks, and follow-up tasks compound into the user's private agent memory.

Power-user prompts like "search Core for prior decisions" or "record this work back to Core" are optional. They are useful for debugging or when the user wants to be explicit, but they should not be the default user experience.