update chromy commands
This commit is contained in:
+4
-4
@@ -10,8 +10,8 @@ The tool should be available in the `$PATH` as `chromy`.
|
||||
|
||||
You have access to these commands:
|
||||
|
||||
- `$ chromy lc` -> Lists the existing collections.
|
||||
- `$ chromy q <collection> <query>` -> Performs a query. Be sure to quote the `<query>` if this is composed by multiple words.
|
||||
- `$ chromy list-collections` -> Lists the existing collections.
|
||||
- `$ chromy query <collection> <query>` -> Performs a query. Be sure to quote the `<query>` if this is composed by multiple words.
|
||||
|
||||
Then use the response from Chromy to enhance the context and give the user a refined response.
|
||||
|
||||
@@ -27,7 +27,7 @@ User query:
|
||||
|
||||
> Search in Chromy information about lovecraft's Dunwich horror.
|
||||
|
||||
Step 1: Get the available collections with `chromy lc`. The output is:
|
||||
Step 1: Get the available collections with `chromy list-collections`. The output is:
|
||||
|
||||
```
|
||||
lovecraft
|
||||
@@ -36,7 +36,7 @@ documents
|
||||
|
||||
Most likely our information is in the `lovecraft` collection. We will use that for the query.
|
||||
|
||||
Step 2: Query using `chromy q lovecraft <query>`. The query _is up to you_, create one keeping into account that this is a raw query on a vector DB. Be concise, extract keywords, avoid noise.
|
||||
Step 2: Query using `chromy query lovecraft <query>`. The query _is up to you_, create one keeping into account that this is a raw query on a vector DB. Be concise, extract keywords, avoid noise.
|
||||
|
||||
Step 3: Get the results, enhance the context, and respond to the user.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user