Clawdi CLI

A CLI that connects local agents to a shared cloud store of sessions, memory, skills and MCP connectors.

  • 107 ★ on the repository
  • Last commit
  • MIT
CLI

Extended access

Why this level

  • Agent sessions, memory and settings are sent to an external service.
  • One installer option runs a script downloaded from the network.
All reasons and checks

clawdi-ai/clawdi

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add cli/clawdi

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Agent sessions, memory and settings are sent to an external service.
  • One installer option runs a script downloaded from the network.

This is third-party code. Review the repository files before installing.

What it does

Clawdi works in two modes. Cloud Agents (Hermes and OpenClaw) run on managed servers, while Connected Agents stay on your computer and sync sessions, skills and MCP settings with the service. For Claude Code and Codex, sessions, skills and MCP are set up automatically, as they are for Hermes; OpenClaw needs MCP added by hand. The `clawdi auth login`, `clawdi setup` and `clawdi doctor` commands sign in, connect an agent and check its state. The repository holds the CLI with an MCP server, a TanStack dashboard, a FastAPI backend and PostgreSQL, so the whole stack can be self-hosted.

Who it is for. People who run Claude Code, Codex and Hermes across several machines and want one session history and a shared skill set.

Good fit when

  • Agent sessions from a laptop and a server should land in one feed.
  • A skill set should live in one place and be handed to agents.
  • A Hermes cloud agent has to run without your own server.
  • A team wants the dashboard and backend self-hosted rather than in someone else's cloud.

Not a fit when

  • Session data must not leave the machine: a purely local agent is needed.
  • The agent runs on Pi or OpenCode and expects skills: only sessions sync for them.
  • You need one small skill, not a platform.

Example request

Connect Claude Code to Clawdi, run `clawdi doctor` and show which skills and MCP connectors synced.

Limitations

Clawdi sends sessions, memory and settings to the service, so check confidential repositories first. Features depend on the agent and run mode: for Pi and OpenCode only sessions sync, with no skills or MCP. See clawdi.ai for Cloud Agent terms. The `install.sh` installer runs a script from the network, so in a strict environment the npm package with Node.js 24 or newer is easier to audit. Run a separate check before connecting work repositories.

How to disable. Run `clawdi uninstall`: it removes local services, agent integrations, sign-in and state. The `--remove-cli` flag also removes the CLI itself. Account data on the service stays.

FAQ

How does a Cloud Agent differ from a Connected one?

A Cloud Agent (Hermes or OpenClaw) runs on a managed Clawdi server. A Connected one stays on your computer and only syncs.

Which agents are supported?

Claude Code, Codex, Hermes, OpenClaw, Pi and OpenCode. Skills work for the first four.

Can it be self-hosted?

Yes. The repository contains the CLI, a FastAPI backend, the dashboard and PostgreSQL; see `AGENTS.md`.

How do I check the connection?

`clawdi doctor` reports the state of services and agent integrations.

What does `clawdi uninstall` do?

It removes local services, integrations, sign-in and state. Account data on the service remains.

Discussion

No questions or reviews yet.

CLI tools

ClawMetry reads the session files agents already write and shows the timeline, tool calls, tokens and cost in one dashboard.

CLIExtended access436Repository stars
Official

MCP server of the self-hosted EmperorClaw panel: Claude Code and Codex read company knowledge, tasks and customers in scope

MCP serverBroad access698Repository stars

One runtime for Claude Code, Codex, OpenCode and more: a run counts as done only when checks the agent did not write pass

CLIBroad access606Repository stars

The clawctl CLI manages a fleet of AI agents on local machines over SSH and Ansible: install, start, upgrade and token tracking.

CLIBroad access67Repository stars

PromptOps keeps Claude Code, Codex and Gemini CLI side by side by project and gives a lead agent MCP to launch helpers

CLIBroad access70Repository stars
Needs a VPN

A compact OpenClaw alternative: a personal assistant on Claude Agent SDK with agents in isolated containers and messengers added via skills

CLIBroad access31.1KRepository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
Clawdi (this card)no107
CC Switchno153,939switches providers and settings of one client; Clawdi syncs sessions and skills across agents
session-migrateno176migrates sessions between tools; Clawdi keeps them in a service and distributes skills

README in short

A short README with an agent support table, sign-in commands and a self-hosting note. Details live in the documentation at docs.clawdi.ai.

README badge

Report a problem