Repository navigation
feat: integrate native OpenJarvis code-assistant TUI - #8205
milesatao-svg wants to merge 7 commits into
Conversation
Copied source evidence 1/1Historical material from original PR #6537, copied for this account migration. Source PR head when copied: Original comment by @nikhilachale on 2026-10-11T08:32:48ZFinal source These are real original VPS AO Electron captures. Unsupported native surfaces remain explicit; no strict runner PASS or unsupported history restore is claimed. Original comment by @nikhilachale on 2026-10-12T16:52:00ZHarness-specific reports, JSON receipts, screenshots and provenance now live on this integration PR branch, rather than the skill PR #6509. Evidence index with embedded screenshots and JSON links. Historical successes, failures and scope limitations remain as recorded. Moving these files does not rerun native/AO testing or upgrade any verdict. This is evidence relocation only. Existing tested source/native hashes and failures are preserved; the documentation commit is not a fresh runtime pass. Applicable checks run in PR CI. Original comment by @nikhilachale on 2026-10-12T18:08:10ZCanonical main conflicts reconciled at Validation is PR CI only; current-head checks are pending until GitHub reports them. This merge does not constitute a new native/AO run or promote historical fresh/restore/provider-role proof. Harness evidence stays on this integration PR; PR6509 remains reusable guidance and linked summaries. Original comment by @nikhilachale on 2026-10-12T18:17:19ZCanonical main conflicts reconciled at Validation is PR CI only; current-head checks are pending until GitHub reports them. This merge does not constitute a new native/AO run or promote historical fresh/restore/provider-role proof. Harness evidence stays on this integration PR; PR6509 remains reusable guidance and linked summaries. Original comment by @nikhilachale on 2026-10-12T20:58:49ZCanonical main conflicts reconciled at Validation is PR CI only; current-head checks are pending until GitHub reports them. This merge does not constitute a new native/AO run or promote historical fresh/restore/provider-role proof. Harness evidence stays on this integration PR; PR6509 remains reusable guidance and linked summaries. Original comment by @nikhilachale on 2026-10-15T06:35:49ZPublished, incomplete qualification — AO UI evidence BLOCKED; not merge-ready. Head Publication report · All ordered screenshot checkpoints Every applicable latest UI checkpoint remains NOT_RUN because this stage had no genuine isolated Electron dependencies and insufficient disk preserving512MiB. API/native receipts are auxiliary, never screenshot substitutes. No image was fabricated. Exact publication-head CI is being checked separately below; old green heads do not qualify edited/merged source. No routine VPS tests, lint, typecheck, gofmt or CI emulator ran. Linux/provider evidence does not establish other OS/provider coverage. Original failures/profiles/logs remain intact privately. No skill6509 writes, production changes, merge, release or deployment. Exact-head CI (2026-10-15T07:12:44.140233+00:00): complete at Original comment by @Meraj-08 on 2026-10-20T09:31:04ZScreenshotsSpawn Workers -
Original comment by @nikhilachale on 2026-10-21T07:14:19ZFresh testing-only retest starting for Original comment by @nikhilachale on 2026-10-21T07:26:48ZBounded TESTING-ONLY retest: BLOCKED — integration incomplete. AO runtime NOT_RUN; strict runner FAIL at infrastructure startup. AO UI attachment evidence: BLOCKED. Tested source/frontend SHA: Recorded comparison main SHA: Build/native provenance and first failures. Linux amd64; Node v24.21.0, npm 11.19.0, Go go1.27.1. Fresh native Native safe probes on 2026-10-21 UTC (PASS means command completion, not provider/auth conformance):
The model table contains genuine cloud row IDs Distinct real attempts; later observations do not erase first failures:
No further retries or AO diagnostic were attempted: there is no current AO binary and the native workspace-proof prerequisite failed. Native startup also warned that optional Capacity and actual UI. Initial free disk 834 MiB; setup measurement 822 MiB, required floor 700 MiB. Pinned Electron 44.7.0 archive alone is 122,998,223 bytes (117.3 MiB), before extraction and 1,497 pinned packages. Dependencies absent. Serial Go build guard fired near the floor; observed free space 710 MiB, with another observation 708 MiB while teardown completed. Only 56 MiB of this worker's abandoned build temp was removed after exact-process checks; no shared cleanup. Post-cleanup free space about 763 MiB. RAM total 3,906 MiB; initial available 2,535 MiB, later 2,427 MiB. Reproduction/current-status receipt. Existing matching credential was resolved from the known authorized native store in memory, passed only in the child environment to isolated native probes (and prepared for the owned daemon), never argv/config/logs/public receipts. Original accepted profiles and native installation stayed unchanged. The independently derived contract SHA-256 is {"schemaVersion":1,"agents":{"openjarvis":{"binary":"<native-bin>/jarvis","versionArgs":["--version"],"integration":{"args":["chat","--help"],"expect":"--agent"},"session":{"args":["ask","--engine","cloud","--model","glm-5.3-flash","--agent","orchestrator","--tools","file_write","{prompt}"],"proofFile":"LOCAL_AUDIT_PROOF.json"}}}}No fabricated interrupt or restoredReady contract: process-local native history has no exact-load command, and Ctrl-C catching alone does not establish executing-tool child reaping. Native model table was independently parsed; the generic runner's text-line mode cannot truthfully treat Rich headers/borders as model IDs, so its model-command field was omitted. These strict gates remain NOT_RUN, not PASS. # In the pinned tested backend, with existing caches and isolated runtime output:
GOMAXPROCS=1 GOFLAGS=-p=1 GOMEMLIMIT=384MiB go build -ldflags='-s -w' -o <runtime>/bin/ao ./cmd/ao
# Use a fresh report basename and runtime-local TMPDIR; credential is env-only.
node <staged-skill>/scripts/audit_ao.mjs --agent openjarvis --repo <tested-source> --ao <runtime>/bin/ao --local-contract <runtime>/contract-current.json --report <runtime>/attempts/strict-001/report --startup-timeout-seconds 15 --timeout-seconds 30The build invocation is shown for reproduction; this attempt was disk-guard terminated and produced no binary. Reusing an old binary/report would not qualify this SHA. Completion matrix. Source-only observations are labelled; none fill live/UI gaps.
Complete screenshot checkpoint index. Created before any UI action. Every row has screenshot unavailable / attachment BLOCKED: actual Electron capacity blocked and no approved GitHub attachment uploader. Zero captures exist; the private attachment queue is empty. No public screenshot checkpoint passes. Pre-session page identities, capture timestamps, serving binary hashes, session/generation and image hashes are unavailable because those screens were never run, not reconstructed after cleanup.
Chat subjourneys explicitly NOT_RUN: new Chat task, shared composer/follow-up and streaming, output/history/native load, approve, reject, witnessed active-tool Stop, UI reconnect, daemon/host recovery, Kill/restore/new instructions, negative capability/restore controls. No OpenJarvis ACP driver is registered; native Current-head CI only. All routine unit/race/lint/vet/typecheck/build-fixture/runner-fixture suites were CI ONLY; none were run locally. Live minimal backend build and native commands above are separate. Fresh checks read at 07:21:35 UTC: 25/25 check runs completed/success at the tested SHA; zero failing or pending check runs. Legacy combined-status API returns pending with zero status contexts; no missing context/job is invented. These checks do not prove authenticated provider, AO runtime or current-head Electron journeys. Reported jobs:
Cleanup and next action. Cleanup receipt at 2026-10-21T07:24:16.818214+00:00: PASS for owned teardown. All 10 command PID/kernel-start identities checked; zero same-identity survivors or owned process-group descendants. Strict runner finalized with daemonStarted=false / stopped=true; its selected loopback port refuses connection. No AO session, Electron, production restart or global stop existed. Both native witness files remain absent; this is failed task proof, not a delayed-command cancellation test. Git source remains clean, including untracked files; native installation modified-file count is zero. Retained operational evidence stays exclusively outside Git in this PR's sibling runtime: sanitized logs/receipts, native-source fingerprints, derived contract, isolated noncredential config/state and empty workspaces, strict report/issue files, full checkpoint index and empty attachment queue. No evidence/PNG committed or uploaded elsewhere. Unresolved: provision enough disk while preserving the floor; resolve provider quota through the account owner without resetting login; qualify the configured custom model route separately (ask currently rejects it); rebuild this exact head; rerun the strict audit with a fresh basename; independently verify actual AO readiness/models/providers/permissions/TUI/refusals and all supported UI/Chat/reviewer paths. Source-only docs/catalog/permission discrepancies remain for authorized product work, not this worker. The parent must attach any future safe actual AO images through an approved route; AO UI attachment evidence stays BLOCKED. PR-description link to this new comment is pending the parent; description was not changed. No full integration PASS is claimed. Original comment by @illegalcall on 2026-10-23T18:37:06ZIndependent runtime validation at
|
| Area | Result | Observed in the native Electron app or the lab daemon |
|---|---|---|
| Harness row without uv | PASS | Settings → Harness → OpenJarvis (official avatar): "Not installed – uv was not found on PATH. Install uv, then retry." Models: "Install OpenJarvis to see its models." |
| In-app install | PASS | "Available via uv tool" → Install → Installing… → Verifying… (~40 s) → v1.0.4, executable ~/.local/bin/jarvis, Authentication Unknown. For a moment after Verifying, the panel showed "jarvis was not found on PATH" before it settled (low). |
| Setup / onboarding | DEFECT | After a fresh install with no key or config, Account shows Unknown with no setup action. The UI only offers Set up OpenJarvis (jarvis quickstart) when auth is unauthorized, or as a re-login when authorized/configured. The docs page tells users to run it from Harness settings, but it can't be reached in this state. |
| Setup output on Apple silicon | DEFECT / integration | Running jarvis quickstart natively in the lab home (M1) wrote [engine] default="mlx" and default_model="qwen3.5:2b". AO's install plan doesn't include MLX, and the overlay keeps the user's engine. The native fallback then crosses the local/cloud boundary, so every AO session started with "Default engine 'mlx' is unavailable; using 'nim'" · Engine nim · Model qwen3.5:2b. A task in that state would go to NVIDIA NIM with a local model id. Quickstart itself sent its built-in test prompt ("Say hello in one sentence.") to NIM without any key and got a 404, yet still printed "Setup complete!". That was the only prompt any part of this test sent to a model endpoint, and it was rejected; there was no authenticated inference at all. |
| Models (no key) | Consistent with scope | Native jarvis model list: 83 nim rows, 0 cloud rows. AO: "openjarvis model discovery returned no models"; the New Task model menu only offers "Refresh models". |
| Task launch (TUI) | PASS | New Task (agent picker "OpenJarvis · Auth unknown"), empty prompt → terminal session even though the app's default interface is Chat. argv: jarvis chat --agent orchestrator, under ao agent-process supervise, cwd = session worktree. The tab showed Idle at the native You>. |
| Programmatic input refusals | PASS | ao send with multiline input, /help, a You> marker, a Confirm: marker, leading whitespace, 3001 bytes, or a tab each returned AGENT_INPUT_REJECTED with a specific reason. The native composer stayed empty. |
| Non-default permission mode | DEFECT (safe direction) | With project permissions=bypass-permissions, the spawn was accepted. argv was unchanged and the overlay [security] was identical to native (enforce_tool_confirmation=true). The docs say only the default mode is supported, but ErrAgentPermissionModeUnsupported is never returned. This is a documentation/behaviour mismatch in the safe direction: no safety bypass was observed, and native confirmations stay enforced. |
| Chat mode | Unsupported, correctly refused | ao spawn --mode chat → SESSION_MODE_UNSUPPORTED: openjarvis has no chat driver; no session was created. The terminal tab menu offers no "Switch to chat UI". |
| Kill / archive | PASS | Archive → confirm → POST /kill 200. The session's pty-host, supervisor and jarvis exited and its clean worktree was removed. A second OpenJarvis session was untouched (same PIDs, still idle). |
| Restore | Unsupported, correctly refused | POST /restore → 409 AGENT_RESTORE_UNSUPPORTED "openjarvis native chat history is in memory; start a new session explicitly", shown inline; no agent or pty process started. Low: the refused restore recreated the clean session worktree and left it behind. |
| Config overlay | Note | data/agents/openjarvis/<sid>/config.toml (mode 0600) copies 10 of 11 native config sections verbatim and adds the AO instruction prefix and the code-assistant tools. Whatever the user keeps in config.toml gets duplicated into AO data. The lab config held only empty placeholders, so this is a design note, not a demonstrated secret leak. |
Environment-blocked or not run (no provider route):
- a real task with a follow-up and its file effects
- whether
AGENTS.mdproject instructions are actually consumed - the native
Confirm:approve/reject flow, and send-while-active refusal - active-turn cancellation (Ctrl-C); not advertised by the PR's docs either
- models/auth with a real key, and the rejected-key "not connected" state
- completing a provider switch (needs a second installed, signed-in agent; the switch entry is Developer Mode only)
- the update/version-refresh path
Lab-only environment notes (not this PR):
predev's wake-helper Swift compile fails on this host's Command Line Tools (Swift 5.8.1 / SDK 13.3), so the app was launched with the AGENTS.md lab recipe instead.- The lab app opened an unrelated
gh auth loginpanel at startup; I closed it without signing in.
Footage: pr6537-openjarvis-lifecycle.mp4 is renderer-only content from the isolated Electron window, captured via CDP screencast: no OS window frame, no audio, 31.6 s, 80 real frames, all decoded and privacy-reviewed. It shows New Task → OpenJarvis REPL (mlx→nim fallback banner) → Archive → "TERMINAL ENDED / [process exited]" → Restore → the 409 refusal. The screenshots show the uv-missing state, the installed state with Unknown auth and no Setup action, and the session banner.
pr6537-openjarvis-lifecycle.mp4
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
🏆 Review leaderboardNov 5–12, 2026 · UTC
Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded. Show 6 more reviewers
|
Account migration verification
|
Resolve conflicts against main adf9f6a: - drop the cloud/internal/worker/script_steps_test.go edit; the control plane left this repository in OrchestratorInc#7352 - keep main's scriptStepTimeoutUnit rename, update-notice test and prompt-readiness loop; re-add openjarvis to the CLI, DTO, installer, OpenAPI and generated schema harness lists - renumber the unshipped OpenJarvis migration to 20261114171639069 so it follows main's newest migration, and base its test there Integrate with main's newer harness surfaces: - request rendered-screen prompt readiness through main's RenderedScreen hint; the adapter had dropped the old RequiresRenderedActivity hook, so the unterminated "You> " composer was never matched - reuse main's renderedReadinessRuntime fake instead of redeclaring it - offer the provider keys the native cloud engine reads (OrchestratorInc#7312) - give OpenJarvis a neutral Usage tone so AGENT_HUES stays exhaustive Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…diff - require a whole `jarvis --version` line to equal the pinned "jarvis, version 1.0.4" instead of a substring match, which also accepted 1.0.40 or a lookalike `jarvis`; give `ao doctor` the same expected version prefix - correct the docs: every AO permission mode runs with native security, and provider keys can be saved for AO in Harness settings - rename the avatar licence to the LICENSE-<id>.txt convention - drop the committed research reports, receipts and screenshots; they remain at the original-commit links in the PR description Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Current-head update and ao-agent-harness receipt (2026-11-14 17:34 IST)Head: What changed in this update
Receipt (per skill step)
CIAll four workflows on this head (CI, Public boundary, gitleaks, Harness release feeds) are Open risks
Not merge-ready: live TUI audit, UI audit and approved CI are all still required. |
nikhilachale
left a comment
There was a problem hiding this comment.
Changes requested. Reviewed PR #8205 at 9a4b218453 against main. The adapter, migration, reconcile repair, install plan, catalog parser and API/UI registration follow the existing Hermes-style harness conventions. Four required changes are inline:
- The submission witness only accepts a screen that ends at the echoed line. Any native output after Enter makes a delivered send report unconfirmed, and AO input stays locked until kill/restore.
- The agent-failure marker check in
DetectTerminalActivitymarks the session Blocked whenever the marker is anywhere in the 40-line viewport, including after a fresh emptyYou>prompt. - AuthStatus reads provider keys with
os.Getenv, bypassing the readiness ctx overrides (authprobe.Getenv), so the reported status can disagree with what sessions receive. ErrAgentPermissionModeUnsupportedis never returned, so its mapping andTestEveryPermissionModeUsesNativeDefaultsare vacuous.
Optional, not required:
- Consider reusing the
authproberedirect/scheme guards inprobeProviderKey. In net/http, customx-api-key/x-goog-api-keyheaders survive cross-host redirects. openjarvis.pngis about 393 KB; a downscaled asset would be lighter.- The
LOGOSentry is placed first instead of in the surrounding order.
The shared conpty/surface.go resize change still needs the maintainer decision and cross-harness live proof the PR already lists. This was a read-only review: I did not run tests or builds.
… auth - confirm a submission where the baseline's empty composer was, aligned below the baseline history, and ignore the turn output and new prompt printed after the echo; before, any output after Enter left the send unconfirmed and blocked AO input until kill/restore - judge the agent-failure marker only after the last prompt, so a fresh empty prompt below an earlier failure is idle again - read provider keys and OPENAI_BASE_URL through authprobe.Getenv, so a key AO withholds from OpenJarvis sessions is not probed - remove the never-returned ErrAgentPermissionModeUnsupported and its mapping; the permission test now stubs the binary and asserts the same argv for every mode Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nikhilachale
left a comment
There was a problem hiding this comment.
Approved. I re-reviewed PR #8205 at 5e109bdf47, looking at the fix commit since 9a4b218453. All four requested changes are resolved:
- Submission witness:
TerminalMessageObservednow lines the screen up with the baseline history above the composer that was empty, then requiresYou> <message>at that row. Rows printed after the echo and the next empty prompt are ignored, so a delivered send no longer locks AO input. Repeated history picks the least-scrolled match and fails closed. New tests cover output after the echo, a new prompt, scrolled history, a padded echo row, and an identical earlier turn. - Failure marker: the marker now only counts after the last column-zero prompt, or anywhere when there is no prompt. A fresh empty prompt reads as Idle again, and the submitted line itself is excluded.
- Auth environment: every key and
OPENAI_BASE_URLlookup on the auth path goes throughauthprobe.Getenv(ctx, ...). A new test covers routed and unrouted keys that AO withholds. - Unused sentinel:
ErrAgentPermissionModeUnsupported, its mapping and its test row are removed, with no references left. The permission test stubs the binary and checks the same argv for every mode.
Optional, not required:
- A long submitted line that wraps can put the failure marker on a continuation row below the prompt, which would read as Blocked. Reserving that marker in
validateLine, as is already done forYou>andConfirm:, would close this. - The earlier optional notes still apply: the
authproberedirect guards, the asset size, and theLOGOSorder.
The shared conpty/surface.go resize change and the live TUI/UI audits are still open PR checklist items. They are outside this code review. This was a read-only review: I did not run tests or builds.









Current head, 2026-11-14 IST:
5e109bdf47(native-review fixes for the input witness, failure marker, withheld-key auth and the unused permission sentinel; all 4 threads resolved), with mainadf9f6a303merged in (no history rewrite). GitHub reports MERGEABLE. Draft, not merge-ready. Receipt and change list.Supported scope: the native TUI only. There is no native session ID or restore (typed
AGENT_RESTORE_UNSUPPORTED), and no Chat, switching, handoff or reviewer. Input is one plain line; every AO permission mode runs with native security.Open checks:
action_requiredand need maintainer approval for fork runstui_native_id,tui_restoreactivity-dispatchtouchpoint as not applicable (no native hooks; terminal detection)conpty/surface.goresize change. It affects every TUI harness on every OS and needs cross-harness proof (Codex and Claude Code inline frames after a shrink, at least on Windows)Research reports and screenshots were removed from the diff; the historical links below still resolve to their original commits.
Code changes: +962 -13
Tests: +564 -15
Others: +563 -4
What
feat: integrate native OpenJarvis code-assistant TUI
Original PR description, preserved
Rebase follow-up, 2026-10-22: Current head
1a9055a5d, rebased as a consolidated integration onto mainc3d22031e. Retains Hermes registration and main terminal-admission protections, regenerates API types for both harnesses, separates daemon test helpers, and covers 39 installer harnesses. The unmerged OpenJarvis migration uses timestamp20261022042122070; upgrade/downgrade tests retain a Hermes session. CI follow-ups fix an inherited duration-variable lint name, keep the cloud heartbeat fixture line unfinished, and align the update-notice test with its existing safe View details fallback after an installer query error (no production UI change). Backend build/vet, Linux-target lint (zero findings on an LF-normalized temporary copy), focused admission/ConPTY/auth/installer/migration/setup-timeout checks, API drift, both frontend typechecks, 8 avatar tests, all 54 update-notice tests, and all 161 Product UI tests pass locally. Full Windows suites remain non-green: renderer rerun has 492 passing and 24 failing files (8667 passed, 213 failed, 8 skipped tests), including packaging/path/runtime/symlink cases; backend also has platform/environment failures. Linux/race, native macOS, Docker and browser gates require CI. Atd32353aa2, 23 of 24 CI checks passed; its sole failure was the now-corrected notice assertion. Current-head CI is complete: all 24 checks passed at1a9055a5d(checks); GitHub reports MERGEABLE. Historical native/UI qualification limits remain unchanged.Lint follow-up, 2026-10-22:
9145086c3fixes the two Linux CI lint findings inopenjarvis/auth.go: usehttp.NoBodyfor GET requests and explicitly discard the response-body close error. Auth-focused tests pass locally. Full Windows backend tests and lint are not green (platform/PATH/symlink and CRLF findings); the existing OpenJarvis workspace-path assertion also fails on the unchanged PR head. Linux/race suites are unavailable locally (no WSL/Docker or CGO). Those conflicts were resolved by the subsequent rebase described above. Historical qualification limits below remain in effect.Binary assets: 4 (excluded from line counts).
Current publication, 2026-10-15:
6a7edfa2a0b0ca1918446597de78fdb4584c68aa. Incomplete qualification; AO UI evidence BLOCKED; not merge-ready. Main conflicts reconciled. Exact-head CI is recorded below; no local routine suites.Published typed restore/input/permission refusal handling and current-main reconciliation. Historical runtime77574094 demonstrated file/follow-up effects, child cancellation and fresh Kill/no-late/control isolation. Independent project instructions failed; post-cancel send was unconfirmed and was never retried. History is in memory: native ID/exact restore/Chat remain unsupported; no replacement identity was invented.
Current report and scoped evidence. Historical runtime/source attribution is retained there.
Exact-head CI (2026-10-15T07:12:44.140233+00:00): complete at
6a7edfa2a0b0ca1918446597de78fdb4584c68aa— 25 SUCCESS (25 reported; 25 expected including the merged Go aggregate gate). Current checks. MergeabilityMERGEABLE, merge stateBLOCKED; draft handoff. CI does not qualify missing native/UI/provider/OS gates. Canonical main subsequently advanced to48c4ef5e with only two non-overlapping preview-process files; GitHub reports this head mergeable. These completed checks belong to the stated publication head, not a newly rebuilt merge with that later base.Preserved earlier description (historical status, validation and evidence snapshots)
Binary assets in this source snapshot: 4 (excluded from line counts).
Official native code-assistant orchestrator TUI; scoped plain single-line input. In-memory history has no native ID/restore; restore, Chat, switch and handoff refused.
Current status
Current source snapshot:
77574094445328af21209f6d32bde40a6cb03143(basedb77f945db58ce1d9970e99e7e9b68396f38c78b). Open for review; GitHub mergeabilityMERGEABLE, merge stateBLOCKED. Exact-head CI: pending (12 successful, 11 queued/running, 0 unsuccessful among 23 reported checks). CI run 1 · CI run 2 · CI run 3 · CI run 4. Green source CI does not establish current native/UI runtime proof or full integration readiness.This fix created only clean isolated source worktrees and temporary review reports; it created no AO/native sessions, provider profiles or owned runtime processes. No local build, gofmt, test, fixture, provider or UI run was performed.
Historical runtime build: Historical AO/UI source
a4bc98eb0a759b4bcf38cf7a6481c45a9ac77315; official OpenJarvis CLI1.0.4 fixed upstream source0eb7811df96cf139e6bd6d7fcc9b5cc4ff1418ff. Final008 and earlier004/006/007 are distinct; native binary fingerprint is not supplied in the reviewed relocated manifest. Report · evidence index, original receipts, image/provenance hashes. Receipt SHAs/bytes are unchanged. Linux/VPS proof is not Windows/macOS native proof. Runner SHA2568887aa2e7101b9e6d3950bfca08ffddf2e1e6c1c3f1d030c8dec2676443aecearemains historical where reported; manual/standalone proof is not a strict runner PASS.Changes since runtime proof: Source maps the unmodified official OpenJarvis circular PNG to the avatar, with pinned upstream source, Apache-2.0 license and authors notices in the sidecar. Actual current-avatar rendering and native/UI journeys are NOT_RUN. Current-main reconciliation preserves the integration and upstream migration ledger; current source/CI state is recorded above.
The matrix separates current verification from recorded historical passes;
NOT_RUNdoes not erase those passes. Excluded interfaces/manual model input are deliberate supported-scope decisions.Historical implementation and evidence
Official native jarvis chat --agent orchestrator preserves SystemPromptBuilder/native safety through additive private configuration. Input is plain single-line, at most3000 UTF-8 bytes; control characters, slash commands, ambiguous prompt markers and uncertain pending delivery are refused. Native confirmation remains intact and blocks ordinary sends; generic HTTP500/refusal UX with request IDs is a known limitation. AO observation cadence is30s, separate from native settlement. Native shell AO routing persisted a session checkpoint. Native Rust rate-limiter warning/model-discovery/install limitations remain documented; no strict runner PASS is claimed. Historical source a4bc98e had 23/23 checks green after unchanged-head rerun of TestKillReq. Native001–003/AO004 routing-resize,006 later approved rerun/late artifact and007 wrong configured project failures remain separate from final008.
historical receipt 1
Reproduction and retained-original limitations
The pinned reports/JSON retain action/result, file/token effects, process identity, cancellation, native-history continuity and capture assertions. A complete sanitized executable reproduction bundle is not established for every manual helper: exact helper bytes/hash and invocation, applicable local-contract bytes/hash with probe argv and interrupt/readiness/draft-cleanup settings, and complete native/AO fingerprints are unavailable where not recorded in the linked receipts; recoverability of those original inputs is unknown. No missing command, contract, hash or result is invented. Later reproductions must use a new attempt and cannot replace original failed/missing evidence.
Recorded owned-process/session/daemon/Electron cleanup is historical. Source worktrees, native profiles/history, dirty scratch workspaces, binaries and raw logs were reported retained privately; a complete current inventory/location/hash and recoverability of every original class are unavailable in the public record. Current recoverability is unknown; this reporting fix reconstructs no missing input and silently substitutes none. Share sanitized artifacts only; exclude credential stores, raw DBs and provider-profile directories. Preserve the retained failures and original screenshots.
Why
The contributor is moving this harness submission to @milesatao-svg. The linked source preserves the implementation and review history.
Before / After
1a9055a5dd2256a87e6002d98f6e3f80b3eb2fac1a9055a5dd2256a87e6002d98f6e3f80b3eb2facOriginal product behavior and existing UI evidence are included in the preserved description and copied evidence comments.
How
Copy the source head into
milesatao-svg/agent-orchestrator:codex/copy-pr-6537-openjarvisand target upstreammain.Testing
Historical test results and screenshots are reproduced in the evidence comments with their original sources. Fresh validation is tracked by this PR's GitHub checks.
Checklist
Account migration verification
1a9055a5dd2256a87e6002d98f6e3f80b3eb2fac.milesatao-svg/agent-orchestrator:codex/copy-pr-6537-openjarvis. Base:main.