PUBLIC EVIDENCE, CARRIED INTO YOUR NEXT SESSION

Keep the reasoning
with the work.

Use Tide from Claude Code or Codex to save the public evidence behind a decision, then recheck that evidence before changing your integration.

A local bridge to the same service

The agent kit runs a local stdio MCP server. It calls the same bounded public research endpoints as this website. Source fetching and model reasoning run on the Tide service; you do not supply Telem, Tavily, model, Redis or signing keys.

Tide's agent kit keeps Ripple-compatible tool and archive names (ripple_* MCP tools, the ripple-board-v1 archive format and ripple-agent-kit.zip), so existing Ripple setups keep working.

This is a local source distribution. It is not an npm package or marketplace listing. Native Claude Code and Codex invocation must be verified separately; this page is not a compatibility certification.

Connect a trusted project

After downloading and reviewing the kit, extract it to a permanent local directory. Node 22 or newer is required. The optional setup helper uses Python 3.11 or newer. Run from the extracted kit directory with your project path and the operator's actual verified deployment origin:

python3 scripts/connect-agents.py \
  --project "/absolute/path/to/your-project" \
  --base-url "https://YOUR-VERIFIED-TIDE-DEPLOYMENT" \
  --agent both

The first command is a dry run. Review its proposed changes, then run the same arguments with --apply to install the project connection. Replace both placeholders with your own paths and the verified service URL.

python3 scripts/connect-agents.py \
  --project "/absolute/path/to/your-project" \
  --base-url "https://YOUR-VERIFIED-TIDE-DEPLOYMENT" \
  --agent both --apply

The helper merges the ripple entry into .mcp.json for Claude Code and .codex/config.toml for Codex. It installs portable skills into .claude/skills/ and .agents/skills/, preserves unrelated settings, rejects conflicts and keeps private configuration backups outside the repository. Choose --agent claude or --agent codex for a single client.

Verify the connection in the client

  1. Open a new ordinary trusted Claude Code or Codex session in the configured project. Use /mcp to inspect the connection.
  2. Explicitly ask the agent to call ripple_status and ripple_list_boards. A configuration listing alone does not prove invocation.
  3. Invoke /ripple-research in Claude Code or $ripple-research in Codex, or ask for a public-source board directly. Tool prefixes can vary by client.
  4. Before revisiting a decision, read the board and use ripple_refresh_board with the expected current local revision. ripple_get_board reads history without checking sources.

Normal host permissions and organization policies still apply. Skills and MCP annotations do not grant authority. Tide does not edit your repository, run shell commands, read arbitrary local files or upload your code.

Two local libraries. Explicit transfer.

Web workspace

Boards live in this browser's IndexedDB. Another browser or device starts empty. Clearing site data deletes that local library.

Agent vault

The connector uses private local files, separated by service origin. The helper also isolates by project. Vault files are not encrypted; sessions and users with access to that local directory may read them.

Browser boards do not automatically appear in the agent vault. Export a ripple-board-v1 JSON archive from one interface, then explicitly import it into the other. Imported evidence remains historical and unverified, including archives with snapshot: null. Rebuild from permitted live public sources before calling those facts fresh.

Research only when you ask

There is no background polling, scheduled monitoring, cross-device sync, anonymous cloud library or public remote MCP endpoint. Refresh is an explicit operation. Questions, URLs and necessary source excerpts reach Tide, Telem, Tavily (selected URLs only) and the configured model provider. The same supported-source restrictions and shared usage quotas apply to agent requests.

By default, the connector bounds each process to 12 admitted billable operations and each HTTP request to 55 seconds, with up to 50 local boards. Failed attempts may use allowance. It never retries a timeout, provider failure or quota rejection automatically. Do not restart it or rotate cookies to evade limits.

Recover or disconnect

On a revision conflict, read the latest saved board and reconcile before writing. If revalidation is required, preserve the historical board and explicitly rebuild from the original question and public URLs. If the vault is busy, stop the competing process; do not remove a lock while a client is using it.

To uninstall, remove only the ripple MCP entry and the tworipple-* skill directories, or unload the optional local Claude plugin. Preserve unrelated client configuration. Local boards remain until you explicitly delete them or the vault. Deleting a browser board does not delete agent copies or exported archives.