@agent-crm/cli 0.0.1 → 0.0.3

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 (2) hide show
  1. package/README.md +14 -4
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,14 +1,14 @@
1
1
  <div align="center">
2
2
 
3
- <img src="assets/header.png" alt="agent-crm">
3
+ <img src="https://cdn.shopify.com/s/files/1/0748/5902/0324/files/header_c7055774-5f0b-4794-85f1-15ac9a5d2a25.png?v=1778036454" alt="agent-crm">
4
4
 
5
5
  </div>
6
6
 
7
- Claude is now running your GTM. Your lead lists live in CSVs because you want to move fast with claude code, but existing CRMs were built for humans, not agents. Their MCPs slow you down, bloat your context, and kill your usage limits.
7
+ Claude is running your GTM and your leads live in CSVs. Spreadsheets fall apart around 30 deals in: you lose track of who said what, what's open, and what's next. CRMs solve that, but they were built for humans clicking through UIs, not agents writing SQL.
8
8
 
9
- Agent CRM gives your agent a structured backend it can query, edit, diff and validate, fast.
9
+ Plug Claude into your CRM via MCP and the schema torches your context, every action is a network round-trip, and you blow through your usage limits. Salesforce and HubSpot are shipping their own CLIs, but they end at the deal record — the scrapes, enrichment runs, and half-cleaned lists that fed it live somewhere else. You can't replay how a deal moved through stages, see what your last scrape pulled in and what it didn't clean up, or pick up where last weekend's list-building session left off.
10
10
 
11
- The source of truth is a portable `.acrm` file. UIs, CLIs, scripts, and agents all operate on it and you can send it around like any other file.
11
+ Agents work best on files. Agent CRM is a portable `.acrm` file your agent can query, edit, diff, and version pipeline, scrapes, and enrichments, all in one place.
12
12
 
13
13
  ```txt
14
14
  ┌──────────────┐
@@ -20,6 +20,16 @@ The source of truth is a portable `.acrm` file. UIs, CLIs, scripts, and agents a
20
20
  └────────────┘ └─────────────┘ └───────────────┘
21
21
  ```
22
22
 
23
+ ## What's in a `.acrm` file?
24
+
25
+ A `.acrm` file is a **SQLite database** with a change-history layer ([Lix](https://lix.dev)) on top. That means:
26
+
27
+ - **No proprietary format.** Open it with any SQLite client (`sqlite3 pipeline.acrm`) and your data is right there in standard tables.
28
+ - **Every write is a versioned checkpoint.** Like git for your CRM — branch to run an experiment, diff to see what changed, revert if Claude mangles a row.
29
+ - **It's just a file.** Copy it, email it, commit it, sync it through Google Drive. No server, no account, no migration tool needed if you ever walk away.
30
+
31
+ If you can read SQLite, you can read your CRM. That's the whole guarantee.
32
+
23
33
  ## Quickstart
24
34
 
25
35
  Install the CLI:
package/package.json CHANGED
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "name": "@agent-crm/cli",
3
- "version": "0.0.1",
3
+ "version": "0.0.3",
4
4
  "description": "Headless CRM for claude code — versioned, queryable, scriptable",
5
5
  "type": "module",
6
6
  "bin": {
7
- "acrm": "./dist/bin/acrm.js"
7
+ "acrm": "dist/bin/acrm.js"
8
8
  },
9
9
  "files": [
10
10
  "dist"