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
Copy file name to clipboardExpand all lines: README.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,11 @@ Bridge build/dev process output to AI coding sessions automatically.
14
14
15
15
In vibe coding workflows, you run an AI coding tool in one terminal and build commands in another. When errors occur, you manually copy-paste logs into the coding session. `devtap` automates this feedback loop.
16
16
17
-
Two common cases make this especially painful:
17
+
Three common cases make this especially painful:
18
18
19
19
1. Multiple local dev processes (frontend + backend + worker) that you need to keep an eye on and fix quickly.
20
20
2. Multiple coding agents working on the same project, where you want them to analyze the same failures in parallel and compare findings.
21
+
3. Build/test runs on remote machines (CI, dev boxes) whose output you need to feed back to a local coding agent.
21
22
22
23
## Quick Start
23
24
@@ -119,7 +120,7 @@ Zero-dependency JSONL files at `~/.devtap/<session>/<adapter>/pending.jsonl`. Ea
For persistent history, SQL-based filtering, and richer statistics. With a remote GreptimeDB instance, Terminal A and Terminal B don't even need to be on the same machine — capture build output from a CI server or remote dev box and consume it from your local AI coding session.
123
+
For persistent history, SQL-based filtering, and richer statistics. With a remote GreptimeDB instance, the build and the AI tool don't even need to be on the same machine — see [Cross-machine builds](#advanced-usage) for details.
123
124
124
125
See [GreptimeDB installation guide](https://docs.greptime.com/getting-started/installation/greptimedb-standalone/) for more options.
**Multi-adapter fan-out** — when multiple AI tools are installed, build output is automatically delivered to all of them. Each tool independently consumes its own copy.
186
187
188
+
**Cross-machine builds** — with a shared [GreptimeDB](#greptimedb-optional) instance, the build and the AI tool can run on different machines. Use `--session` to give both sides the same logical session name:
189
+
190
+
```bash
191
+
# Machine A (CI / remote build server)
192
+
devtap --store greptimedb --session myproject -- make
0 commit comments