# How To Use Core

For the user, Core should mostly disappear after setup. They should ask their agent for normal work, and the connected agent should 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 agent should handle the Core loop internally:

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.