@getlore/cli 0.5.0 → 0.5.2

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@getlore/cli",
3
- "version": "0.5.0",
3
+ "version": "0.5.2",
4
4
  "description": "Research knowledge repository with semantic search, citations, and project lineage tracking",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -8,6 +8,26 @@ user-invocable: false
8
8
 
9
9
  Lore is a research knowledge repository available via MCP. It stores documents, meeting notes, interviews, and decisions with full citations back to original sources. Use it to ground your work in evidence and preserve important context.
10
10
 
11
+ ## First-Time Setup
12
+
13
+ If Lore is not installed yet, you can set it up for the user.
14
+
15
+ 1. **Install**: `npm install -g @getlore/cli` (requires Node.js 18+)
16
+ 2. **Ask the user** for their **email address**
17
+ 3. **Ask for API keys** — present these two options:
18
+ - **Recommended**: Tell the user to run these commands themselves (keys stay out of chat history):
19
+ ```
20
+ export OPENAI_API_KEY="sk-..."
21
+ export ANTHROPIC_API_KEY="sk-ant-..."
22
+ ```
23
+ Then run: `lore setup --openai-key $OPENAI_API_KEY --anthropic-key $ANTHROPIC_API_KEY --email <email> --data-dir ~/.lore`
24
+ - **Convenient but riskier**: The user can paste keys directly into this chat and you run setup with them. Warn the user that keys shared in chat may be stored in conversation history.
25
+ 4. **Send OTP**: Run the setup command — this sends a 6-digit code to their email and exits
26
+ 5. **Ask the user** for the **6-digit code** from their email
27
+ 6. **Complete setup**: Re-run the same command with `--code <code>` appended
28
+
29
+ After setup, Lore works autonomously.
30
+
11
31
  ## MCP Tools
12
32
 
13
33
  | Tool | Cost | Use For |
@@ -7,6 +7,26 @@ description: Search and ingest knowledge from Lore — a research repository wit
7
7
 
8
8
  Lore is a research knowledge repository available via MCP. It stores documents, meeting notes, interviews, and decisions with full citations back to original sources. Use it to ground your work in evidence and preserve important context.
9
9
 
10
+ ## First-Time Setup
11
+
12
+ If Lore is not installed yet, you can set it up for the user.
13
+
14
+ 1. **Install**: `npm install -g @getlore/cli` (requires Node.js 18+)
15
+ 2. **Ask the user** for their **email address**
16
+ 3. **Ask for API keys** — present these two options:
17
+ - **Recommended**: Tell the user to run these commands themselves (keys stay out of chat history):
18
+ ```
19
+ export OPENAI_API_KEY="sk-..."
20
+ export ANTHROPIC_API_KEY="sk-ant-..."
21
+ ```
22
+ Then run: `lore setup --openai-key $OPENAI_API_KEY --anthropic-key $ANTHROPIC_API_KEY --email <email> --data-dir ~/.lore`
23
+ - **Convenient but riskier**: The user can paste keys directly into this chat and you run setup with them. Warn the user that keys shared in chat may be stored in conversation history.
24
+ 4. **Send OTP**: Run the setup command — this sends a 6-digit code to their email and exits
25
+ 5. **Ask the user** for the **6-digit code** from their email
26
+ 6. **Complete setup**: Re-run the same command with `--code <code>` appended
27
+
28
+ After setup, Lore works autonomously.
29
+
10
30
  ## MCP Tools
11
31
 
12
32
  | Tool | Cost | Use For |
@@ -2,6 +2,26 @@
2
2
 
3
3
  Lore is a research knowledge repository available via MCP. It stores documents, meeting notes, interviews, and decisions with full citations back to original sources. Use it to ground your work in evidence and preserve important context.
4
4
 
5
+ ## First-Time Setup
6
+
7
+ If Lore is not installed yet, you can set it up for the user.
8
+
9
+ 1. **Install**: `npm install -g @getlore/cli` (requires Node.js 18+)
10
+ 2. **Ask the user** for their **email address**
11
+ 3. **Ask for API keys** — present these two options:
12
+ - **Recommended**: Tell the user to run these commands themselves (keys stay out of chat history):
13
+ ```
14
+ export OPENAI_API_KEY="sk-..."
15
+ export ANTHROPIC_API_KEY="sk-ant-..."
16
+ ```
17
+ Then run: `lore setup --openai-key $OPENAI_API_KEY --anthropic-key $ANTHROPIC_API_KEY --email <email> --data-dir ~/.lore`
18
+ - **Convenient but riskier**: The user can paste keys directly into this chat and you run setup with them. Warn the user that keys shared in chat may be stored in conversation history.
19
+ 4. **Send OTP**: Run the setup command — this sends a 6-digit code to their email and exits
20
+ 5. **Ask the user** for the **6-digit code** from their email
21
+ 6. **Complete setup**: Re-run the same command with `--code <code>` appended
22
+
23
+ After setup, Lore works autonomously.
24
+
5
25
  ## MCP Tools
6
26
 
7
27
  | Tool | Cost | Use For |
@@ -2,6 +2,26 @@
2
2
 
3
3
  Lore is a research knowledge repository accessible via MCP (Model Context Protocol). It stores documents with full-text search, semantic search, and citation tracking. Content is deduplicated, embedded for retrieval, and organized by project.
4
4
 
5
+ ## First-Time Setup
6
+
7
+ If Lore is not installed yet, you can set it up for the user.
8
+
9
+ 1. **Install**: `npm install -g @getlore/cli` (requires Node.js 18+)
10
+ 2. **Ask the user** for their **email address**
11
+ 3. **Ask for API keys** — present these two options:
12
+ - **Recommended**: Tell the user to run these commands themselves (keys stay out of chat history):
13
+ ```
14
+ export OPENAI_API_KEY="sk-..."
15
+ export ANTHROPIC_API_KEY="sk-ant-..."
16
+ ```
17
+ Then run: `lore setup --openai-key $OPENAI_API_KEY --anthropic-key $ANTHROPIC_API_KEY --email <email> --data-dir ~/.lore`
18
+ - **Convenient but riskier**: The user can paste keys directly into this chat and you run setup with them. Warn the user that keys shared in chat may be stored in conversation history.
19
+ 4. **Send OTP**: Run the setup command — this sends a 6-digit code to their email and exits
20
+ 5. **Ask the user** for the **6-digit code** from their email
21
+ 6. **Complete setup**: Re-run the same command with `--code <code>` appended
22
+
23
+ After setup, Lore works autonomously.
24
+
5
25
  ## Core Concepts
6
26
 
7
27
  - **Sources**: Full documents (meeting notes, interviews, Slack threads, specs, etc.)