# Manage clients and import history Canonical: https://hypaware.ai/docs/clients Use `hyp setup` to choose which AI clients to record. Setup configures those clients and imports supported session history. Ollama records explicitly routed new requests and has no history import. You can also run `hyp attach ` to configure a client and `hyp backfill ` to import history. Ollama attach enables recording and prints [explicit host recipes](https://hypaware.ai/docs/integrations/ollama/index.md#route-a-cli-or-sdk-client); it does not edit client files or the calling shell's or service's `OLLAMA_HOST`. [LangGraph](https://hypaware.ai/docs/integrations/langgraph/index.md) is also an explicit application setup: choose it under **Customize**, or run `hyp client attach langgraph` later and add the printed JavaScript or Python callback to your application. It recovers events the callback saved while the collector was down, but does not import old checkpoints or automatically discover projects. [NanoClaw](https://hypaware.ai/docs/integrations/nanoclaw/index.md) requires an explicit local installation root in the `@hypaware/nanoclaw` plugin configuration. It is not offered in the setup picker. Once configured, it recovers local v2 Claude transcripts every five minutes, including subagents. [Cursor Cloud](https://hypaware.ai/docs/integrations/cursor/index.md#cursor-cloud-agents-beta) uses the bundled Cursor plugin with explicit `hyp cursor-cloud connect` and `start` commands inside the managed VM. Local Cursor attachment does not connect Cloud agents. Use `hyp cursor-cloud disconnect` to revoke the VM grant; ordinary local history-import instructions do not apply to Cloud capture. ## Choose and check a client [VS Code (GitHub Copilot)](https://hypaware.ai/docs/integrations/copilot/index.md) uses the setup id `copilot`. Attach enables its native database exporters; reload VS Code afterward. Capture runs every minute for local single-folder workspaces, within VS Code's native history retention. [Factory Droid](https://hypaware.ai/docs/integrations/droid/index.md) uses the setup id `droid`. Attach installs native transcript-change hooks; restart Droid afterward. Recovery imports local session files every five minutes. Hosted sessions without local transcripts are not captured. [Grok Build](https://hypaware.ai/docs/integrations/grok/index.md) uses the setup id `grok`. Attach adds a HypAware hook file under `~/.grok/hooks`; restart Grok Build afterward. Recovery imports local session files every five minutes. [Goose](https://hypaware.ai/docs/integrations/goose/index.md) uses the setup id `goose`. It reads Goose's local session database read-only and changes nothing in Goose, so there is nothing to restart. Check it with `hyp status`; `hyp client status` does not list it. [Crush](https://hypaware.ai/docs/integrations/crush/index.md) uses the setup id `crush`. It reads each project's Crush database read-only and changes nothing in Crush, so there is nothing to restart. Check it with `hyp status`; `hyp client status` does not list it. [Mastra Code](https://hypaware.ai/docs/integrations/mastracode/index.md) uses the setup id `mastracode`. It reads Mastra Code's local database read-only and changes nothing in Mastra Code, so there is nothing to restart. Check it with `hyp status`; `hyp client status` does not list it. ```sh hyp setup hyp client status hyp client status codex ``` On an existing installation, choose **Reconfigure** to add a client. Team-managed choices are locked; local additions remain yours to configure. Each client's capture behavior, requirements, and limits are on its [integration page](https://hypaware.ai/docs/integrations/index.md), with its status. Available integrations depend on active plugins and the installed version. Check `hyp plugin list` and `hyp backfill list` for your installation. Raw proxy sources do not configure an AI client; use a client integration for conversation capture. ## Attach and verify new activity For a configured client, preview its changes and apply them: ```sh hyp attach codex --dry-run hyp attach codex hyp client status codex hyp status ``` Attach is safe to repeat and preserves unrelated client settings. Start a new client process so it reads the updated configuration, complete a short turn, then check `hyp query overview` or search for a distinctive phrase with `hyp query grep`. Capture and cache visibility can take time to settle. For Ollama, starting a new process alone does not route it through capture: use the [printed CLI host or SDK constructor](https://hypaware.ai/docs/integrations/ollama/index.md#route-a-cli-or-sdk-client). For missing recordings, see [troubleshooting](https://hypaware.ai/docs/troubleshooting/index.md#no-new-recordings). ## Bring in existing history Discover provider IDs and preview the scan before importing: ```sh hyp backfill list hyp backfill codex --since 2026-09-01T00:00:00Z --dry-run hyp backfill codex --since 2026-09-01T00:00:00Z hyp cache status ``` Both `codex` and `--since` are optional. Omit the provider to import from all enabled providers; use `--since` to choose a start date. Without it, the import uses the configured history window. `backfill --dry-run` scans and projects without writing, so it previews the result but is not a cheap probe. Inspect each provider's output because one provider can fail while others succeed. > **Caution:** Import writes the local cache. If exports are configured, eligible imported > rows can subsequently leave through those sinks. Apply your > [privacy markings](https://hypaware.ai/docs/privacy/index.md) before importing sensitive history. Some integrations run scheduled recovery automatically. A positive `backfill.window_days` limits both join-time backfill and scheduled recovery; widening it can make older history eligible on the next sweep. `hyp detach` stops a client's schedules. The adapters differ in how `backfill.on_join` affects schedules, so consult the [recovery reference](https://hypaware.ai/docs/cli-reference/index.md#scheduled-recovery-sweeps-and-backfillwindow_days) before changing those settings. ## Stop capture or keep it local ```sh hyp detach codex --dry-run hyp detach codex ``` Detach stops recording this client: no new sessions from it reach the cache, including the scheduled transcript imports, and the running daemon picks this up without a restart. Detach also reverses the client's managed settings where supported. For Ollama, [verified detach](https://hypaware.ai/docs/integrations/ollama/index.md#stop-and-resume-ollama-recording) keeps the running capture host forwarding without recording; it does not change a client's host. Recorded history is kept; [`hyp privacy purge`](https://hypaware.ai/docs/privacy/index.md) deletes it. `hyp status` then shows the client as "Not recording". Run `hyp attach codex` to record it again. If team policy requires the integration, detach refuses and changes nothing. To keep a client's recordings local, exclude a directory or session, or delete recorded rows, use [privacy controls](https://hypaware.ai/docs/privacy/index.md). For missing recordings, see [troubleshooting](https://hypaware.ai/docs/troubleshooting/index.md). ## Install client skills Setup and `hyp attach` automatically install HypAware's skills in supported clients so your agent can look up recorded sessions. To reinstall the skills: ```sh hyp client skills install ``` This installs skills for all eligible clients. For launching an agent on a question, see [queries](https://hypaware.ai/docs/querying/index.md#explore-recordings-with-your-agent).