You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
semble search "save model to disk" ./my-project --top-k 10
64
64
```
65
65
66
+
If you anticipate doing more than one search, use `semble index` to create an index.
67
+
68
+
```bash
69
+
semble index ./my-project -o my_index
70
+
```
71
+
72
+
You can then reuse this index later on:
73
+
74
+
```bash
75
+
semble search "save_pretrained" --index my_index
76
+
```
77
+
78
+
An index is not automatically updated, so if the code changes significantly, reindex. If you notice stale results while resolving searches to files, reindex.
79
+
66
80
Use `--content docs` to search documentation and prose, `--content config` for config files (yaml, toml, etc.), or `--content all` to search code, docs, and config:
67
81
68
82
```bash
@@ -77,17 +91,20 @@ Use `semble find-related` to discover code similar to a known location (pass `fi
77
91
semble find-related src/auth.py 42 ./my-project
78
92
```
79
93
94
+
Like search, `find-related` also accepts an `--index` argument.
95
+
80
96
`path` defaults to the current directory when omitted; git URLs are accepted.
81
97
82
98
If `semble` is not on `$PATH`, use `uvx --from "semble[mcp]" semble` in its place.
83
99
84
100
### Workflow
85
101
86
-
1. Start with `semble search` to find relevant chunks.
87
-
2. Use `--content docs` for documentation, `--content config` for config files, or `--content all` for everything.
88
-
3. Inspect full files only when the returned chunk is not enough context.
89
-
4. Optionally use `semble find-related` with a promising result's `file_path` and `line` to discover related implementations.
90
-
5. Use grep only when you need exhaustive literal matches or quick confirmation of an exact string.
102
+
1. Index the repo using `semble index -o cached_index`.
103
+
2. Start with `semble search` to find relevant chunks. Pass the index to achieve results faster.
104
+
3. Use `--content docs` for documentation, `--content config` for config files, or `--content all` for everything.
105
+
4. Inspect full files only when the returned chunk does not give enough context.
106
+
5. Optionally use `semble find-related` with a promising result's `file_path` and `line` to discover related implementations.
107
+
6. Use grep only when you need exhaustive literal matches or quick confirmation of an exact string.
semble search "save model to disk" ./my-project --top-k 10
319
336
```
320
337
338
+
If you anticipate doing more than one search, use `semble index` to create an index.
339
+
340
+
```bash
341
+
semble index ./my-project -o my_index
342
+
```
343
+
344
+
You can then reuse this index later on:
345
+
346
+
```bash
347
+
semble search "save_pretrained" --index my_index
348
+
```
349
+
350
+
An index is not automatically updated, so if the code changes significantly, reindex. If you notice stale results while resolving searches to files, reindex.
351
+
321
352
Use `--content docs` to search documentation and prose, `--content config` for config files (yaml, toml, etc.), or `--content all` to search code, docs, and config:
322
353
323
354
```bash
@@ -332,17 +363,20 @@ Use `semble find-related` to discover code similar to a known location (pass `fi
332
363
semble find-related src/auth.py 42 ./my-project
333
364
```
334
365
366
+
Like search, `find-related` also accepts an `--index` argument.
367
+
335
368
`path` defaults to the current directory when omitted; git URLs are accepted.
336
369
337
370
If `semble` is not on `$PATH`, use `uvx --from "semble[mcp]" semble` in its place.
338
371
339
-
## Workflow
372
+
###Workflow
340
373
341
-
1. Start with `semble search` to find relevant chunks.
342
-
2. Use `--content docs` for documentation, `--content config` for config files, or `--content all` for everything.
343
-
3. Inspect full files only when the returned chunk is not enough context.
344
-
4. Optionally use `semble find-related` with a promising result's `file_path` and `line` to discover related implementations.
345
-
5. Use grep only when you need exhaustive literal matches or quick confirmation of an exact string.
374
+
1. Index the repo using `semble index -o cached_index`.
375
+
2. Start with `semble search` to find relevant chunks. Pass the index to achieve results faster.
376
+
3. Use `--content docs` for documentation, `--content config` for config files, or `--content all` for everything.
377
+
4. Inspect full files only when the returned chunk does not give enough context.
378
+
5. Optionally use `semble find-related` with a promising result's `file_path` and `line` to discover related implementations.
379
+
6. Use grep only when you need exhaustive literal matches or quick confirmation of an exact string.
346
380
```
347
381
348
382
### Sub-agent setup
@@ -365,8 +399,14 @@ If semble is not on `$PATH`, prefix the command with `uvx --from "semble[mcp]"`.
365
399
Semble also ships as a standalone CLI. This is useful in scripts or anywhere you want search results without an MCP session.
0 commit comments