snxraven/gnome-jarvis
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Updates
Rolling release / release (push) Successful in 7m42s
Details

Browse Source
This commit is contained in:
snxraven
2026-09-14 14:43:33 -04:00
parent dd8b00a56b
commit 507405c6ca
23 changed files with 397 additions and 392 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/agent-harness-map.md
+7 -10
View File
@@ -1,9 +1,7 @@
# Agent harness map
Source of truth for Jarvis runtime: `vendor/agent-harness/`, copied from
`/home/raven/dev/agent-harness` (`~/dev/agent-harness`). The original extracted
tree remains the upstream working source; the vendored directory is the copy
that ships with this repository.
Source of truth for Jarvis runtime: `vendor/agent-harness/`. That tree is a
copied dependency that ships with this repository (not a symlink).
## Layout and runtime
@@ -74,12 +72,11 @@ The harness does not use an OpenAI-compatible HTTP URL internally. Its
`lib/qvac.js` imports `@qvac/sdk` in-process and calls `loadModel()` and
`completion()`. Jarvis keeps the optional sibling `qvac serve --openai`
provider for external clients and diagnostics, while the cognition bridge
wraps the harness in-process as required by the extracted package.
wraps the harness in-process.
## Computer use
The inspected harness has no first-class portal, AT-SPI, libei, or desktop
computer-use backend. Jarvis therefore supplies those as custom tools from
`computer-use/` and `skills/`, while keeping planning in `agent/loop.js`.
Webcam capture is the same pattern: a Camera portal helper plus one `webcam`
tool.
The harness has no first-class portal, AT-SPI, libei, or desktop computer-use
backend. Jarvis therefore supplies those as custom tools from `computer-use/`
and `skills/`, while keeping planning in `agent/loop.js`. Webcam capture is the
same pattern: a Camera portal helper plus one `webcam` tool.