@nex-ai/nex 0.1.63 → 0.1.64

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 +27 -1
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -29,13 +29,39 @@ npx @nex-ai/nex ask "who is Maria?"
29
29
  nex setup
30
30
  ```
31
31
 
32
- `nex setup` handles everything: API key registration, platform detection, hook installation, file scanning, and config creation. Run it once and you're ready to go.
32
+ `nex setup` handles the base install flow: API key registration or re-keying, platform detection, platform installation, optional first integration connection, file scanning, and config creation.
33
33
 
34
34
  ```bash
35
35
  # Now query your knowledge
36
36
  nex ask "what's the latest on the Acme deal?"
37
37
  ```
38
38
 
39
+ ## Copy-Paste Prompt For Any AI Agent
40
+
41
+ Use this when you want Claude, Codex, Cursor, OpenCode, or another terminal-capable AI agent to do the full Nex bootstrap for you.
42
+
43
+ ```text
44
+ Install and fully bootstrap Nex in this project from start to finish.
45
+
46
+ 1. If the `nex` CLI is missing, install it globally with `npm install -g @nex-ai/nex`.
47
+ 2. If Nex is not authenticated yet, ask me for the email address I want to use for registration, then continue. If Nex is already authenticated, reuse the existing account and key.
48
+ 3. Run `nex setup` and complete the full install flow for every detected AI coding platform in this environment.
49
+ 4. After setup, inspect integrations and connect the first available unconnected integration. Prefer this order when multiple choices are available: gmail, google-calendar, slack, salesforce, hubspot, attio, outlook, outlook-calendar. If OAuth is required, open the browser flow and wait for it to complete.
50
+ 5. Run a fresh file scan for the current directory so the workspace is up to date.
51
+ 6. After the scan finishes, trigger Nex compounding jobs by calling the authenticated `POST https://app.nex.ai/api/developers/v1/compounding/trigger` endpoint for these job types: `consolidation`, `pattern_detection`, and `playbook_synthesis`. Use the active Nex API key from the current environment or the config written by Nex setup.
52
+ 7. Fetch the last 24 hours of insights with the insights endpoint or `nex insight list --last 24h`, then give me a clean digest with sections for Highlights, Risks, Opportunities, Open Loops, and Recommended Next Actions.
53
+ 8. Finish by showing me:
54
+ - what Nex installed
55
+ - which integration was connected
56
+ - how many files were scanned and ingested
57
+ - whether the compounding/playbooks trigger succeeded
58
+ - the formatted 24-hour insight digest
59
+
60
+ Do not stop after partial setup. Only pause if you need my email for registration or if an OAuth flow requires my interaction.
61
+ ```
62
+
63
+ This works best in agents that can run shell commands and open OAuth URLs.
64
+
39
65
  <details>
40
66
  <summary>Manual setup (if you prefer step-by-step)</summary>
41
67
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nex-ai/nex",
3
- "version": "0.1.63",
3
+ "version": "0.1.64",
4
4
  "description": "Nex CLI provides organizational context & memory to AI agents. Connect email, CRM, Slack, meetings, and 100+ tools into one knowledge graph.",
5
5
  "mcpName": "io.github.nex-crm/nex",
6
6
  "type": "module",