dunkirk.sh
snatching amp's walkthrough for my own purposes mwhahaha
traverse.dunkirk.sh/diagram/6121f05c-a5ef-4ecf-8ffc-02534c5e767c
docs: fix readme
+5
-6
README.md
+5
-6
README.md
···
1
1
# traverse
2
2
3
-
[](https://traverse.dunkirk.sh/diagram/6121f05c-a5ef-4ecf-8ffc-02534c5e767c)
3
+
[](https://traverse.dunkirk.sh/diagram/6121f05c-a5ef-4ecf-8ffc-02534c5e767c)
4
+
5
+
> [!NOTE]
6
+
> The canonical repo for this is hosted on tangled over at [`dunkirk.sh/traverse`](https://tangled.org/@dunkirk.sh/traverse)
4
7
5
8
One of my favorite features about [amp](https://ampcode.com) is their walkthrough feature. It runs a sub agent which goes and breaks your repo into parts and then sends it up to amp's services to get rendered into a nice web page! I got curious and ended up dumping the tool prompt for both the walkthrough subagent and the tool prompt that generates the diagram.
6
9
···
43
46
44
47
## Config
45
48
46
-
### json config
47
-
48
49
On macos edit/create `~/Library/Application Support/traverse/config.json`. If you are on Linux then `~/.config/traverse/config.json` (or `$XDG_CONFIG_HOME/traverse/config.json`)
49
50
50
51
```json
···
55
56
}
56
57
```
57
58
58
-
### env vars
59
+
alteratively or suplementally you can use env vars to define the same options:
59
60
60
61
| var | default | description |
61
62
| -------------------- | ----------------------------- | ------------------------------------------ |
···
63
64
| `TRAVERSE_MODE` | `local` | `local` (mcp + web) or `server` (web only) |
64
65
| `TRAVERSE_SHARE_URL` | `https://traverse.dunkirk.sh` | share server url |
65
66
| `TRAVERSE_DATA_DIR` | platform default | sqlite db location |
66
-
67
-
The canonical repo for this is hosted on tangled over at [`dunkirk.sh/traverse`](https://tangled.org/@dunkirk.sh/traverse)
68
67
69
68
<p align="center">
70
69
<img src="https://raw.githubusercontent.com/taciturnaxolotl/carriage/main/.github/images/line-break.svg" />