clawdi 0.5.10 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +8 -3
  2. package/dist/index.js +284 -224
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,7 +1,7 @@
1
1
  <h1 align="center">Clawdi</h1>
2
2
 
3
3
  <p align="center">
4
- <strong>The best home for all your AI agents — environments, sessions, memory, skills, cron jobs, and app connections.</strong>
4
+ <strong>The best home for all your AI agents — Projects, sessions, memory, skills, cron jobs, and app connections.</strong>
5
5
  </p>
6
6
 
7
7
  <p align="center">
@@ -72,6 +72,7 @@ Clawdi is the shared layer underneath:
72
72
 
73
73
  - **Cross-agent memory** — Store durable preferences, decisions, facts, and project context once. Search them from any connected agent.
74
74
  - **Portable skills** — Upload or install agent instructions once, then sync them into every registered agent.
75
+ - **Project sharing** — Share read-only Project access, accept it from the CLI inbox, and explicitly attach accepted Projects to Agents when they should be used at runtime.
75
76
  - **Session sync** — Push local session history to the dashboard for review and recall.
76
77
  - **Vault secrets** — Store secrets server-side and inject them only when running a command.
77
78
  - **App connections** — Hook agents into Notion, Gmail, Drive, Calendar, Linear, GitHub, and more from the dashboard. Tools show up inside every connected agent automatically over MCP.
@@ -108,9 +109,9 @@ The first is autonomy. Agents should work without you at the keyboard.
108
109
  - Remote control for agents on any of your machines.
109
110
  - Automatic memory built from session history.
110
111
 
111
- The second is making Clawdi multi-player. Today every Clawdi belongs to one person. That's the wrong shape for teams.
112
+ The second is making Clawdi multi-player. Project sharing now covers read-only Project access in the CLI/backend; dashboard surfaces and richer team roles come next.
112
113
 
113
- - Shared memory, skills, and connections, with access controls.
114
+ - Shared memory, skills, and connections, with broader access controls.
114
115
  - An agent-to-agent channel for handoff and ask-for-help.
115
116
  - Task tracking that every connected agent can use.
116
117
 
@@ -221,6 +222,10 @@ Each agent has a dedicated adapter in [`packages/cli/src/adapters`](https://gith
221
222
  | `clawdi pull` | Download cloud skills into registered agents |
222
223
  | `clawdi memory list/search/add/rm` | Manage cross-agent long-term memory |
223
224
  | `clawdi skill list/add/install/rm/init` | Manage portable skills |
225
+ | `clawdi project create/list/show/share/share-links/invite/invites/members/leave/unshare` | Manage Projects and read-only sharing |
226
+ | `clawdi inbox [accept/decline/forget]` | Accept invitations and share links |
227
+ | `clawdi agent projects list/attach/detach/move` | View the fixed Agent Project and manage attached Projects |
228
+ | `clawdi project folder link/status/unlink` | Link a local folder to a Project for `clawdi run` vault selection |
224
229
  | `clawdi vault set/list/import` | Manage encrypted secrets |
225
230
  | `clawdi run -- <cmd>` | Run a command with vault secrets injected |
226
231
  | `clawdi doctor` | Diagnose auth, agent paths, vault, and MCP config |