Skip to content

feat: add Tau terminal harness - #6493

Closed
nikhilachale wants to merge 32 commits into
OrchestratorInc:mainfrom
nikhilachale:feat/agent-tau
Closed

nikhilachale wants to merge 32 commits into
OrchestratorInc:mainfrom
nikhilachale:feat/agent-tau

Conversation

@nikhilachale

@nikhilachale nikhilachale commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator

Code changes: +751 -29
Tests: +1415 -6
Others: +5719 -3

Binary assets in the current PR diff: 14 (excluded from line counts).

Adds the pinned Tau terminal harness with native appended private instructions, preserved native/user/project rules, model selection and isolated lifecycle hooks. Chat, reviewers and cross-interface handoff are unsupported; explicit bypass permissions are required.

The actual AO audit exposed and fixed two defects: long multiline messages now reach Tau as one bracketed paste through the final admitted guard write, and exact restore now rejects missing/empty/corrupt/ambiguous/wrong-cwd native history instead of accepting metadata alone. Released-native CI exercises both boundaries. A fake-profile environment test and lint style issues found by CI are corrected for the new full run.

Draft: mixed live result. Current CI artifact e1ef49b12712b6c5fc17e595f931bc28296dd66f passed a GLM-4.7 ordinary fresh task with private/project/user actions, cwd, initial once and AGENTS preservation; executing-shell Escape, independent AO Kill/control isolation and missing-history rejection also passed. Exact native identity and new runtime generation restored, with NEW managed instructions confirmed by the supported read-only native SDK, but two ordinary restored tasks left the OLD private token: restored consumption FAIL. Current GLM-5.3-Flash partial fresh failure and earlier failures remain separate. The positive control changes task length/model; it does not identify the sole cause or erase failures.

Harness-owned audit report and real AO screenshots. Runtime source, native wheel/118-file fingerprint, serving PID/executable SHA, native-ID digest, generation and cleanup are recorded there. UI source is separately 3e80348c; later fixture/switch-style/evidence commits never relabel the old runtime binary. Controlled native/source payload role is system; authenticated third-party wire role was NOT_CAPTURED.

Validation is GitHub PR CI only; no routine VPS/Mac suites ran. All applicable current-head checks must finish before readiness. No per-harness report/JSON/PNG is added to PR6509.

2026-10-21 update: merged upstream main 7c83bd68c1e60c85b6a90e3ffa1340c859e4a3ff in f2c85a89f7. Resolved the shared harness registrations and launch-environment changes, moved the unmerged Tau migration to timestamp 20261021090000000, and regenerated the API artifacts. The daemon build and focused merge/migration regressions pass locally. Full local validation is not green: installed OpenCode discovery times out, the broad session/storage runs exceed their local default timeout, and the broad frontend suite reports multiple failures. Native Executors/New task verification and current-head CI are still in progress. Earlier live limitations above remain applicable.

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

🏆 Review leaderboard

Oct 2–9, 2026 · UTC

Rank Reviewer PRs reviewed Review rounds PR comments
🥇 @illegalcall @illegalcall 27 45 10
🥈 @ronishrohan @ronishrohan 19 22 16
🥉 @Vaibhaav-Tiwari @Vaibhaav-Tiwari 16 20 11
4 @Prasad-D-Ware @Prasad-D-Ware 10 27 1
5 @axisrow @axisrow 8 10 54
6 @Rishet11 @Rishet11 7 17 2
7 @mohakchakraborty2004 @mohakchakraborty2004 7 7 1
8 @nikhilachale @nikhilachale 6 14 3
9 @Pritom14 @Pritom14 5 5 4
10 @codebanditssss @codebanditssss 4 4 2

Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded.

Show 5 more reviewers
Rank Reviewer PRs reviewed Review rounds PR comments
11 @neversettle17-101 @neversettle17-101 3 4 0
12 @harshitsinghbhandari @harshitsinghbhandari 2 4 0
13 @whoisasx @whoisasx 2 2 0
14 @AgentWrapper @AgentWrapper 1 3 0
15 @ApexYash11 @ApexYash11 1 2 0

@OrcInc OrcInc added this to the Agents & orchestration milestone Oct 10, 2026
@OrcInc OrcInc added comp/daemon Go daemon, process lifecycle, and backend control plane. enhancement New feature or request labels Oct 10, 2026
@nikhilachale

nikhilachale commented Oct 10, 2026 •

Copy link
Copy Markdown
Collaborator Author

Evidence correction from the skill packaging review: the historical system_prompt_restore token was included in the initial standing instructions before the first turn. Its later appearance proves that token remained available after restore; it does not prove fresh instruction delivery or reinjection. The original 17/17 lifecycle result is a recorded runner result, not verified evidence for all 17 intended behaviors. Refreshed instructions remain unproven for this historical run. The reusable runner is being corrected to introduce a fresh token only after confirmed kill and before restore; fixture validation of that change is separate from real-provider validation, which has not been rerun. Original counts and artifacts below are retained for traceability.


Tau 0.4.7 — VPS audit report, 2026-10-10

Functional lifecycle: 17/17 PASS. CI on the audited commit: 24/24 PASS. Overall audit: BLOCKED. This is diagnostic lifecycle coverage; a full strict audit PASS is not claimed.

Audited commit: 189ca905dee3264ba5c682590ae04bcd8da88adf. Environment: Ubuntu 24.04 x86_64, the released native CLI, an isolated AO daemon/workspace/profile, and real Z.ai coding-plan calls using glm-5.3-flash. No tests, builds, lint, typechecks or provider execution ran on the user's Mac.

Gate totals: 25 PASS, 2 NOT_RUN, 1 BLOCKED. These are gate counts, separate from the 24 CI checks.

Local CLI

Gate Result Reason
local_binary PASS local executable resolved
local_version PASS local version command succeeded
local_integration PASS local integration probe succeeded
local_session_spawn PASS direct local CLI session produced the requested proof
local_models_list NOT_RUN local model-list command is not defined

AO / AOS11

Gate Result Reason
registered PASS agent is registered
installed PASS AO resolved the installed executable
fresh_probe PASS installation and authentication observations are fresh
authentication BLOCKED Tau has credentials configured, but AO could not verify them.
ao_models_api PASS AO model API listed 917 model(s)
tui_spawn PASS AO created the requested TUI session
proof_file_creation PASS AO_AUDIT_PROOF.json contains valid JSON
correct_working_directory PASS provider reported AO's session workspace
initial_prompt_exactly_once PASS unique initial token was handled once
hidden_ao_instructions PASS provider consumed hidden AO standing instructions
project_agents_md PASS provider consumed project AGENTS.md
activity_status PASS AO exposed ready status and an active→idle transition
second_message PASS second API message produced the requested provider-authored mutation
native_session_id PASS AO persisted a provider-native session identity
cancellation PASS AO terminal mux sent configured input to the observed active session and the same terminal settled
termination PASS kill was acknowledged and termination was confirmed
native_restore PASS AO restored in native mode with the exact provider-native ID
same_ao_session_workspace PASS restore retained the AO session ID and workspace
post_restore_terminal_ready PASS the restored native terminal displayed the configured ready cue on the same terminal generation
post_restore_message PASS post-restore message produced a provider-authored mutation
history_file_continuity PASS native history recall and original proof-file continuity were both observed
system_prompt_restore PASS restore-only hidden standing instruction was observed after restore

Cross-check

Gate Result Reason
model_catalog_consistency NOT_RUN both local and AO model catalogs are required for comparison

AO reports credentials as configured, not provider-verified. Real Z.ai calls succeeded, so this metadata gap is not evidence of an expired login. Tau's provider TSV must not be counted as one model ID per row; native model listing/exact catalog comparison remain NOT_RUN.

The live audit reproduced an ANSI-split composer marker causing a false startup timeout. The readiness fix strips ANSI before matching. VPS regression, session-manager/Tau race suites and pinned released-TUI conformance passed. Earlier renamed-binary hook-path failures and premature post-restore sends were test setup/runner failures; they are preserved separately. Final attempt 6 passed after using the canonical AO executable and waiting for the native composer.

The original strict skill remains unchanged. The separate diagnostic runner continues lifecycle testing only after successful direct native proof and AO installation/freshness checks; it retains the original non-passing auth/model gates. The runner revision used here passed 80/80 fixture tests; subsequent generic improvements passed 91/91.

Audited-head backend/aggregate CI · Pinned released-native conformance

Cleanup confirmed: the created session was terminated and the isolated daemon/native PTY processes stopped. A final audit-wide process scan found no remaining owned test processes. Credentials and raw native IDs are omitted here. Previous failed attempts and controlled comparisons remain preserved in the audit bundle. Real terminal text was captured; screenshots, Electron UI and native non-Linux harness coverage are not claimed.

Evidence identity
  • Final attempt: tau-diagnostic-attempt6
  • Source report: tau-diagnostic-attempt6/report.json
  • Original JSON report SHA-256: d4a17a7476d3f66c4db32fb731309695c2377d4cb93e479fa01f608ce611c17e
  • Audited AO binary SHA-256: ba1d3a51bd48bdf9d89d4e59dcdfa33449f86b72bf3bd0de6923888870187515
  • Diagnostic runner SHA-256: 09070c3086b73d8a5d54b28ab07697dda06b67b23bc3c1ddea4555f7144ec741
  • The retained export includes sanitized report copies, prior attempts, fixture logs, review findings and exact-head CI evidence; export copies hash native/opaque identities and retain original-file hashes.

@nikhilachale

nikhilachale commented Oct 10, 2026 •

Copy link
Copy Markdown
Collaborator Author

Evidence correction from the skill packaging review: the historical system_prompt_restore token was included in the initial standing instructions before the first turn. Its later appearance proves that token remained available after restore; it does not prove fresh instruction delivery or reinjection. The original 17/17 lifecycle result is a recorded runner result, not verified evidence for all 17 intended behaviors. Refreshed instructions remain unproven for this historical run. The reusable runner is being corrected to introduce a fresh token only after confirmed kill and before restore; fixture validation of that change is separate from real-provider validation, which has not been rerun. Original counts and artifacts below are retained for traceability.


Tau 0.4.7 — failed-attempt report, 2026-10-10

The original failures remain preserved even though the final diagnostic run passed all 17 lifecycle gates. The full strict audit remains BLOCKED: AO reports configured credentials, and native model discovery/comparison are NOT_RUN. See the final gate-by-gate report.

All times below are UTC on 2026-10-10. Testing ran on the Ubuntu VPS, with real Z.ai calls; no local Mac checks were run.

Attempt / start Observed failure Cause and resolution Preserved evidence
Strict 1 / 05:44:26 Authentication BLOCKED; dependent lifecycle gates NOT_RUN. AO's configured-only observation does not prove provider-verified auth. Successful direct calls allowed separately labeled diagnostic testing; the strict result was not rewritten. tau-strict-attempt1/report.json
Diagnostic 1 / 05:53:03; 2 / 06:01:58 TUI spawn failed: HTTP 409 SPAWN_TIMEOUT. In attempt 2 the call took 20.978 s. Integration bug: the visible Ask Tau… placeholder was split by cursor SGR styling. Raw-string readiness matching missed it. Fixed by stripping ANSI before matching in 189ca905. The earlier Ring.Tail hypothesis was disproved. tau-diagnostic-attempt{1,2}/report.json; attempt 2 diagnosis.json, terminal-capture/003-plain.ansi, 003-styled.ansi, raw-terminal.ansi
Diagnostic 3 / 06:20:35; 4 / 06:24:54 Spawn remained pending; native startup hooks could not invoke ao. Downstream lifecycle gates were NOT_RUN. Test launcher defect: the prebuilt executable had a noncanonical basename, so native children lacked ao on PATH. A symlink still resolved the renamed executable. A canonical executable/hardlink named ao fixed the fixture; this is not evidence of a production startup race. tau-diagnostic-attempt{3,4}/report.json, source.json, diagnosis.json
Diagnostic 5 / 06:27:00 After exact-ID restore, send returned HTTP 409 SESSION_STARTUP_PENDING; post-restore execution, history and refreshed instructions failed to be proven. Runner readiness defect: restore returned 06:28:08.015; send failed 06:28:08.043; native startup hook succeeded 06:28:09.508. Runner now waits for native readiness before sending. tau-diagnostic-attempt5/report.json, diagnosis.json
Earlier diagnostic model comparison Catalog comparison reported FAIL / no shared model IDs. Invalid model-list fixture: tau providers TSV rows were interpreted as 29 model IDs. This was not a valid model-catalog comparison. Unsupported parsing was removed; final discovery/comparison remain NOT_RUN, not PASS. Original diagnostic reports; attempt-history.json
Diagnostic 6 / 06:39:13–06:42:34 No functional lifecycle failures. All 17 lifecycle gates passed with canonical binary and readiness-aware runner. Gate totals: 25 PASS, 1 BLOCKED, 2 NOT_RUN. All 24 CI checks passed on 189ca905dee3264ba5c682590ae04bcd8da88adf. tau-diagnostic-attempt6/report.json; final-ci.json

Representative original error:

POST /api/v1/sessions -> 409
code: SPAWN_TIMEOUT
message: Session spawn timed out before the agent could start
requestId: vps-linux/vbrD5uxUux-000010

The original native marker was A\x1b[0m\x1b[38;2;111;114;117;48;2;16;20;25msk Tau…. Of 25 plain samples, zero contained the literal marker and 23 contained it after ANSI stripping. This is preserved diagnostic evidence, not a screenshot.

Remaining gaps: configured credentials are authorized for this audit but still not classified as provider-verified by AO; this is not an expired-login finding. Local model listing and exact catalog comparison were not executed with a valid contract.

Screenshot coverage: the historical attempts have real terminal text/ANSI captures, but no PNG screenshots. No rendered log or recreated error image is claimed as an original screenshot.

Evidence paths above are relative to the preserved VPS report directory /home/azureuser/.ao/audits/harness-20261010/reports/. A sanitized report export is retained locally under ao-agent-harness/reports/vps-2026-10-10/, including attempt-history.json; raw terminal captures remain on the VPS. These paths are provenance references, not public downloadable GitHub attachments. Original failed/partial artifacts were not replaced by final passing results.

@nikhilachale

nikhilachale commented Oct 10, 2026 •

Copy link
Copy Markdown
Collaborator Author

The reusable integration/testing skill and consolidated session report are now in #6509.

The report includes two redacted, actual screenshots from the new Open Interpreter early-send reproduction; they are published repository evidence, not historical screenshots of Tau or Neovate. Original captures remain unchanged.

The historical instruction-refresh correction remains explicit: the old system_prompt_restore token was available before the first turn, so the recorded 17/17 result does not prove reinjected/refreshed instructions. The packaged runner now creates and installs a fresh token only after confirmed kill. Its exact commit passed 98/98 fixture tests on the Ubuntu VPS; the strengthened instruction gate has not been rerun against real providers. Auth/model gaps and the observed early-send failure remain unresolved in the historical integration results.

@nikhilachale

nikhilachale commented Oct 10, 2026 •

Copy link
Copy Markdown
Collaborator Author

Fresh current-runner follow-up, all computation and capture on the authorized VPS.

Tau 0.4.7 / Z.ai glm-5.3-flash / TUI / explicit bypass only: tau-002 finished at 2026-10-10T18:30:55.127Z with 25 PASS, 0 FAIL, 1 BLOCKED, 2 NOT_RUN. Functional lifecycle passes; strict overall BLOCKED / diagnostic-only. Auth remains configured, not verified. Native model listing and native/AO comparison remain NOT_RUN. No login, credential changes, or contract relaxation.

The fresh restore-only instruction was introduced through the project API after confirmed kill, read back, then consumed in the restored mutation. Same native ID/workspace, initialized empty composer, model/workspace cue, post-restore mutation and history continuity passed. Native digest a3f87013b77caef5c8860009aea4a55d567173d68e86562b9bed16afd4d8fdad; AO session audit-tau-0fb37380-1. Cancellation is observed active-turn Escape→idle (~0.25s), not proof of already-running subprocess reaping. The restored transcript says the 120-second wait completed; it did not establish cancellation of that shell.

Preserved tau-001: 21 PASS, 4 FAIL, 1 BLOCKED, 2 NOT_RUN. Provider-authored JSON acquired an extra closing brace on the second mutation; second_message, post_restore_message, history_file_continuity and system_prompt_restore failed. No file repair; fresh retry used identical source/pin/profile/contract. Original gate-time screenshot unavailable (API audit preceded GUI); the first image below is a later retained-session capture with its own timestamp. Historical failures remain unchanged. Historical 17/17 labels did not prove fresh instructions; native mirrors did not prove real AO UI.

Tested functional source 189ca905dee3264ba5c682590ae04bcd8da88adf; AO binary SHA-256 4c82435bec3bac6f08b1073d416c683b4035e20721b3d1b6d345a2a09216d4ef; UI source same. Runner SHA-256 8887aa2e7101b9e6d3950bfca08ffddf2e1e6c1c3f1d030c8dec2676443aecea. Evidence-only head b98a1bfb4ebad89a0e6501de204623ab69bb4bb2. Original exact source 24/24 CI successful. Final evidence-head checks tracked separately; no unnecessary full backend race rerun or frontend tsc/OOM retry.

Actual AO Electron, native bridge confirmed, exact target session selected, screenshots inspected for secrets/relevance. Supervisor reopened the same isolated data with the identical verified binary after stopping finalized runner; Tau-002 native digest and restored generation reconfirmed. Tau-001 records retained-session recovery and audit identity, but no explicit capture-time digest/generation recheck; it is failure-state UI evidence. PNGs are actual scrot/Xvfb captures, not terminal mirrors.

tau-001 retained failed proof attempt inside actual AO

Failure capture UTC 2026-10-10T18:26:18.392600Z, PNG SHA-256 6ca864dc3d6fadb1e321f37245bc9d774f103c791826a4b1e8a4b5d4b05bfa56.

tau-002 restored functional diagnostic success inside actual AO

Success capture UTC 2026-10-10T18:32:59.570527Z, PNG SHA-256 1902fbcc696799f3b6cf36d80041e9b7248d35acb93d17cfc988833d7c841f69. Curated gate results, full provenance, native fingerprints and cleanup. Both owned sessions API-killed/termination confirmed; exact Electron/current run-file daemon executable verified before TERM and gone. Original reports/profiles/provenance binaries preserved; unrelated AO state untouched.

Final evidence-head CI verified at 2026-10-10T18:57:28.374670+00:00: 24/24 checks successful on b98a1bfb4ebad89a0e6501de204623ab69bb4bb2. Exact-head check example. Original source CI and final evidence CI are separate records; these are remote workflow results.

@nikhilachale nikhilachale left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Fence composer readiness to the current Tau launch

PromptReadinessHints uses the visible Ask Tau… marker, but waitForPromptReadiness obtains it from Runtime.GetOutput; the tmux implementation captures the last 80 lines with capture-pane -S, and Runtime.Restart explicitly preserves terminal history. When AO performs a fresh fallback/recovery on an existing Tau handle—for example, a live/exited pane whose native session ID was never captured—the prior Tau composer marker is still in scrollback. The very first poll can therefore report ready before the replacement Tau process has mounted its composer, and deliverAfterStartPrompt can paste the saved task into the initializing process, where it may be dropped.

Please fence readiness to the current runtime launch (for example, require the current-generation session_start signal promised by FirstSignalProvesInputReady in addition to the marker), or baseline/clear old pane output before matching. A focused regression test should return stale Ask Tau… output immediately after restart and prove delivery waits for current-launch readiness.

Comment thread backend/internal/cli/spawn.go Resolved
Comment thread backend/internal/cli/doctor.go Resolved
@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Harness-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.

Recorded harness evidence — see scope above

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Canonical main conflicts reconciled at 726047d23be0, preserving previous source/evidence ancestry and every existing harness report/screenshot byte. Reconciliation receipt.

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.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Canonical main conflicts reconciled at 06c78c137e13, preserving previous source/evidence ancestry and every existing harness report/screenshot byte. Reconciliation receipt.

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.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Canonical main conflicts reconciled at 553caad947f0, preserving previous source/evidence ancestry and every existing harness report/screenshot byte. Reconciliation receipt.

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.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Canonical main conflicts reconciled at 96abd39e95a2, preserving previous source/evidence ancestry and every existing harness report/screenshot byte. Reconciliation receipt.

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.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Canonical main conflicts reconciled at 3e80348c14ca, preserving previous source/evidence ancestry and every existing harness report/screenshot byte. Reconciliation receipt.

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.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Canonical main conflicts reconciled at 1f1a6031a909, preserving previous source/evidence ancestry and every existing harness report/screenshot byte. Reconciliation receipt.

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.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Canonical main conflicts reconciled at e1ef49b12712, preserving previous source/evidence ancestry and every existing harness report/screenshot byte. Reconciliation receipt.

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.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Current Tau audit evidence is on this integration branch at 6e788d0086fd: report, original asset hashes/UTC, current missing-history rejection, restored NEW-token failure.

Fresh private/project/user controls, executing Escape, independent AO Kill with live unrelated control, and missing-history guard passed in their exact recorded source/model scope. Restored consumption failed on both an update and separate new-file task despite configured NEW append. Earlier Flash/helper/input/history failures remain visible. Runtime binary is e1ef49b1 (SHA e17dfc12723a…), UI 3e80348c, stock Tau0.4.7 with all118 released Python files matching; authenticated wire role NOT_CAPTURED. PR stays draft; new-head CI is pending.

Actual registered Tau fresh control

Exact native restore with empty composer

Unrelated control still usable after primary Kill

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Fresh testing-only retest starting for tau at current PR head 16709897dc418ae265217b79d9fc0ffc9c389146 using harness skill bfb28b79f90df0a56892e8d8b1d3139dea1148db. One bounded serial attempt (25-minute maximum; eight-minute output-stall watchdog); isolated source/runtime. Previous evidence is historical and will not count as fresh proof. Full 12-area matrix and screenshot checkpoints will follow in a new comment. No implementation, pushes, production restart, or excluded PR changes.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Tau bounded current-head retest — BLOCKED, with CI FAIL. No full integration PASS.

Observed 2026-10-21T07:12:35.781155+00:00; Linux amd64. Tested/current PR head 16709897dc418ae265217b79d9fc0ffc9c389146 (fresh recheck 2026-10-21T07:11:02.570427+00:00); skill bfb28b79f90df0a56892e8d8b1d3139dea1148db. Every staged skill file matched that commit byte-for-byte. Source remained clean/detached; no source/branch changes, pushes, merges, review publication or evidence commits.

AO UI attachment evidence: BLOCKED. No actual Electron captures and no approved uploader. The full checkpoint index below is intentionally incomplete. PR-description link to this new evidence comment is pending parent action.

Runtime identity and actual attempts:

  • Native released CLI: tau 0.4.7; actual installed entrypoint SHA256 c2bb2a8b895236bb3789cd3420bd4ad986c366cdea91d3fb95ad155b996f7c7c. Original inventory launcher hash a85200514b8e0f1ffb3d7fa5724c68b87e173b7ae03cb50d6ed2e290e1461807 is a wrapper, not the underlying entrypoint. Fresh isolated credential-free launcher hash 26eb3c664c3182623475f0c8224ecdecbc70e5c84f7b9220fe90070b0d228048. Default metadata: provider zai-audit, kind openai-compatible, model glm-5.3-flash; effective authenticated routing is NOT_RUN.
  • AO: ao version dev, Go 1.27.1; executable SHA256 f0b8e56871e95d087b3e64b58386c8b0f89a8310de11144d16549a188cbff148. Embedded VCS revision equals tested head, vcs.modified=false. Serial go build -o /runtime/bin/ao ./cmd/ao: 2026-10-21T07:03:52.544443+00:00 → 2026-10-21T07:04:34.725536+00:00, exit 0. Limits: GOMAXPROCS=1, GOFLAGS=-p=1, GOMEMLIMIT=384MiB; Node 24.21.0 heap limit 384MiB. No routine local unit/race/lint/vet/typecheck/fixture/build-validation suites were run.
  • Fresh safe native --version, --help, providers, and exact TSV model projection all exited 0. Native and AO catalog count: 917, including zai-audit/glm-5.3-flash; this is local configured/catalog evidence, not 917 authorized models. Projection reads the actual 11-field native TSV and emits exact provider/model IDs; its private __audit-models dispatch is test plumbing, not an upstream flag.
  • strict-001: 2026-10-21T07:05:23.550137+00:00 → 2026-10-21T07:05:40.533164+00:00, exit 1, summary BLOCKED. Binary/version/integration/model probes, registration and installed gates PASS. First strict blocker: fresh_probe: readiness observations are not fresh. Probe HTTP 200 returned authStatus: unknown; readiness HTTP 200 returned auth unknown, freshness stale, checkedAt: null, auth_check_inconclusive, effective readiness unknown. AO catalog/lifecycle gates then NOT_RUN by strict policy. Report SHA256 f0ddd87632cbbcfe64d696d1c66fe4d5853c5fb1d175081ee73ba29330780158. No diagnostic runner attempt: mandatory native provider proof and fresh AO readiness prerequisites were unavailable.
  • Credential/provider witness: BLOCKED. The required provider key was absent from the worker environment. Automatic approval review rejected loading the existing matching provider key route. That rejection was not bypassed; credential content was not read/copied/printed, no login/account reset was attempted, and no provider turn was made. This is an operational authorization blocker, not a native credential rejection. Approval remains unanswered at this receipt. Independent native success has not been invented or used to upgrade AO auth.
  • api-001: OPERATOR/PROBE FAIL, retained. API off/on writes succeeded, then the private helper raised KeyError: harnessDefaults because empty preferences are omitted. Exact owned daemon shut down exit 0. No product fix. api-002: limited API PASS for 917-model catalog/refresh, off/on and bulk save/readback, and persisted disabled model after an owned daemon restart. This supplies no actual picker/UI/effective-provider proof. Explicit Chat create returned 409 SESSION_MODE_UNSUPPORTED: tau has no chat driver; subsequent session inventory was empty. Negative reviewer request against a nonexistent scratch session returned 500 REVIEW_OPERATION_FAILED; this is preserved and does not prove supported reviewer behavior or a truthful reviewer-capability rejection.
  • native-safe-001: unprompted real native TUI startup observed Ask Tau…, then intentionally SIGTERM/reaped (exit -15), no task/provider call. PID 1490665/kernel-start 161231190; raw bounded native stream retained privately, not presented as AO UI. Native --mode acp exited 2 before provider execution; help/source expose Pi-compatible RPC rather than ACP. Fresh startup is not restored/empty-composer proof; no restoredReady regex was fabricated.
  • Desktop preflight BLOCKED: frontend dependencies absent; 1,497 lockfile packages. Free disk was 846MiB, only 146MiB above the required 700MiB floor. Official pinned Electron 33.4.11 archive measured 106,366,319 compressed bytes and 274,653,350 unpacked bytes (261.93MiB) across 74 entries, before npm dependencies. Archive directory was measured by a streamed read without disk writes after Range metadata failed HTTP 501. npm ci and actual Electron launch NOT_RUN to preserve the floor; no old source/dependency tree/screenshot was reused. All captures and attachments unavailable. Final measured free disk at cleanup: 832MiB.
    Reproduction receipt (paths normalized; no credential-store/profile paths or values published):
GOMAXPROCS=1 GOFLAGS=-p=1 GOMEMLIMIT=384MiB go build -o /runtime/bin/ao ./cmd/ao
# Use the isolated native launcher and minimal copied configuration; do not load a denied key route.
TMPDIR=/runtime/tmp PATH=/runtime/bin:$PATH NODE_OPTIONS=--max-old-space-size=384 \
node /pinned-skill/scripts/audit_ao.mjs --agent tau --repo /clean-tested-source \
  --ao /runtime/bin/ao --local-contract /runtime/contract-strict.json \
  --report /runtime/attempts/strict-001/report --startup-timeout-seconds 60 --timeout-seconds 30

Contract original-byte SHA256 1ed9c270abc07ec8d9a7e1ffda16c621a64dae255c89f23399ffda69e21f6b07; path-normalized content below (path normalization changes bytes/hash). session deliberately absent because credential loading was denied; native source-derived intended safe session args are --print --approve --mode json {prompt}, never executed. restoredReady absent because fresh startup/settled/draft/restored matching samples are missing. Escape derives from pinned native binding. Profiles were limited to known provider/catalog config copies, mode 0700/0600.

{
  "schemaVersion": 1,
  "agents": {
    "tau": {
      "binary": "/runtime/bin/tau",
      "versionArgs": [
        "--version"
      ],
      "integration": {
        "args": [
          "providers"
        ],
        "expect": "zai-audit"
      },
      "models": {
        "args": [
          "__audit-models"
        ],
        "format": "json"
      },
      "aoModelsPath": "agents/{agent}/models",
      "interrupt": {
        "input": "\u001b",
        "settleTimeoutMs": 5000
      }
    }
  }
}

Completion matrix:

Area Supported scope Verification Proof or reason
Registration and UI Registered Tau TUI, API/DTO/product identity; actual desktop BLOCKED API registered/installed PASS. Actual Agent Harness and New Task UI unavailable because fresh Electron cannot fit above the disk floor.
Models Native configured catalog and both AO model surfaces BLOCKED Native and AO each expose 917 exact provider/model IDs; refresh and off/on/bulk API readback plus daemon-restart persistence PASS. Both UI surfaces, picker effects and effective launched selection NOT_RUN.
Providers Explicit native provider metadata and account/routing controls BLOCKED Native TSV identifies default zai-audit, OpenAI-compatible kind, glm-5.3-flash, and required key name. Credential source approval rejected; effective routing/provider turn NOT_RUN. AO add/edit/remove/account UI not exercised.
Setup AO installer and Account setup/error/retry NOT_RUN Display-safe plans read: uv tool install tau-ai==0.4.7 and documentation-only /login guidance. Installs/upgrades/login/account changes prohibited; no install/setup action executed. CI release-feed lookup fails 404.
Readiness Installed Tau 0.4.7 on Linux; native and AO readiness BLOCKED Strict fresh_probe BLOCKED: authentication unknown/stale, auth_check_inconclusive, no checkedAt. Native unprompted Ask Tau cue observed, but no verified provider authorization. Existing matching key was not inherited; automatic approval rejected loading it.
Identity and logo Tau product label/avatar BLOCKED Product label Tau registered; current AgentAvatar has no Tau asset and falls back to an initial. Native UI branding/license verification unavailable; fallback intent is not documented here.
TUI and Chat TUI; independently assessed ACP/shared Chat BLOCKED Unprompted native TUI startup PASS only. Strict AO turns NOT_RUN. Native --mode acp rejects with exit 2; installed CLI/source offers Pi-compatible RPC, not ACP. AO Chat is unregistered and explicit request returns 409 SESSION_MODE_UNSUPPORTED; broader RPC Chat wiring NOT_IMPLEMENTED.
Reviewer Separate AO reviewer registry, pane, run/result/cancel/rerun NOT_RUN Tau is absent from reviewer registry/DTO. No native special reviewer capability qualified; headless prompt mode exists but suitability/wiring unfinished. Negative request against nonexistent scratch session returned generic 500, not a successful capability rejection. No GitHub review/publication executed; publication prohibited.
Permissions and instructions Explicit bypass only; additive standing/project instructions NOT_RUN Source rejects default, accept-edits, auto and allow/deny restrictions; native Escape binding confirmed. No authenticated AO turn, effective permission behavior, independent instructions or restored fresh token consumption qualified.
Lifecycle Active-tool cancel, Kill/archive, exact restore, Kanban, reconnect NOT_RUN Strict prerequisite blocked all dependent turns. No executing-command PID/kernel witness, delayed-side-effect check, provider history/restore or continuation. API preference persistence across daemon restart is not native session recovery.
Evidence Current build, distinct attempts, UI checkpoint publication BLOCKED Strict and independent receipts retained outside Git; 24 required screenshot rows retained plus Chat/reviewer subjourneys. Zero actual Electron captures. AO UI attachment evidence: BLOCKED; no approved uploader and private queue is empty.
CI and handoff Current-head remote checks, conflicts, cleanup and parent handoff FAIL 26 completed check runs: 25 success, live-feeds failure (Tau pinned package PyPI URL 404). Legacy combined status says pending with zero contexts; no pending check-run job observed. PR mergeable=false/dirty. Owned processes gone; source clean. PR-description evidence link pending parent.
Screenshot checkpoint index, created before actions. Shared provenance: tested frontend/source head above; actual desktop never launched, so capture time/session/generation/image hashes and attachment URLs do not exist. Every capture is unavailable; no private PNG counts as published proof.
Checkpoint/substep Action → observed result Functional status Screenshot/attachment
--- --- --- ---
harness-listed Open Agent Harness → no actual Electron surface BLOCKED BLOCKED: unavailable
install-offer Inspect install action → no UI; API advertises uv pinned install BLOCKED BLOCKED: unavailable
install-run Start/progress/result → not started NOT_RUN BLOCKED: unavailable
auth-before Inspect existing account → no UI; AO unknown/stale BLOCKED BLOCKED: unavailable
auth-action Start Login/Setup and return → not started NOT_RUN BLOCKED: unavailable
auth-ready Fresh verify and provider turn → no turn BLOCKED BLOCKED: unavailable
auth-maintenance Change/logout/retry → not acted NOT_RUN BLOCKED: unavailable
harness-models List/refresh → 917 API models; UI unavailable BLOCKED BLOCKED: unavailable
model-visibility Off/on/bulk/save/reload/pickers → API persistence PASS only BLOCKED BLOCKED: unavailable
provider-management Browse/configure/switch provider → metadata read only BLOCKED BLOCKED: unavailable
task-agent Board New Task → not opened BLOCKED BLOCKED: unavailable
task-model Choose model → no UI selection/launch BLOCKED BLOCKED: unavailable
task-running Submit/card/initial output/settle → not submitted NOT_RUN BLOCKED: unavailable
task-followup Normal composer follow-up → not sent NOT_RUN BLOCKED: unavailable
task-cancel Executing tool/Stop/settle → not started NOT_RUN BLOCKED: unavailable
kill-action Archive control/confirm/terminated → not acted NOT_RUN BLOCKED: unavailable
archived Show exact archived entry → no entry NOT_RUN BLOCKED: unavailable
restore-action Restore exact history/empty composer → not acted NOT_RUN BLOCKED: unavailable
kanban-return Same restored card/continuation → not acted NOT_RUN BLOCKED: unavailable
chat Shared New Task/composer/stream/approval/Stop/recovery → not run NOT_RUN BLOCKED: unavailable
reviewer-select Select Tau reviewer/target 6493 at tested head → unavailable NOT_RUN BLOCKED: unavailable
reviewer-running Review/run/cancel/error/retry → no execution NOT_RUN BLOCKED: unavailable
reviewer-result Result/verdict/rerun → no result NOT_RUN BLOCKED: unavailable
reconnect-cleanup UI reconnect/recovery/final cleanup → no UI BLOCKED BLOCKED: unavailable
chat/new-task Not exercised NOT_RUN BLOCKED: unavailable
chat/followup-stream Not exercised NOT_RUN BLOCKED: unavailable
chat/load-history Not exercised NOT_RUN BLOCKED: unavailable
chat/approve Not exercised NOT_RUN BLOCKED: unavailable
chat/reject Not exercised NOT_RUN BLOCKED: unavailable
chat/cancel-active-tool Not exercised NOT_RUN BLOCKED: unavailable
chat/ui-reconnect Not exercised NOT_RUN BLOCKED: unavailable
chat/daemon-host-recovery Not exercised NOT_RUN BLOCKED: unavailable
chat/kill-restore-instructions Not exercised NOT_RUN BLOCKED: unavailable
chat/negative-restore-capabilities Not exercised NOT_RUN BLOCKED: unavailable
reviewer/target-head Not exercised NOT_RUN BLOCKED: unavailable
reviewer/run Not exercised NOT_RUN BLOCKED: unavailable
reviewer/result Not exercised NOT_RUN BLOCKED: unavailable
reviewer/cancel Not exercised NOT_RUN BLOCKED: unavailable
reviewer/rerun Not exercised NOT_RUN BLOCKED: unavailable
Current-head CI, read from GitHub (no local routine validation). The check runs refer to this exact implementation head and were completed on 15 October; reading them today is not a new CI rerun. released-tui is a localhost fixture-provider contract test, not authenticated external-provider proof. No pending/failing job is hidden below. Legacy combined status endpoint separately reports pending with an empty status-context list.
Check Current-head state Proof
--- --- ---
build-test completed / success job
native (windows-latest) completed / success job
native (ubuntu-latest) completed / success job
native (macos-latest) completed / success job
container completed / success job
sqlite-race (2) completed / success job
lint completed / success job
sqlite-race (1) completed / success job
sqlc-drift completed / success job
windows-workspace completed / success job
cloud-build-test completed / success job
session-store-race completed / success job
released-tui completed / success job
backend-core (0) completed / success job
chat-race (1) completed / success job
api-drift completed / success job
sqlite-race (3) completed / success job
backend-core (1) completed / success job
sqlite-race (0) completed / success job
test completed / success job
mac-update-helper completed / success job
chat-race (0) completed / success job
linux-proof-artifact completed / success job
scan completed / success job
live-feeds completed / failure job
renderer-smoke completed / success job
The failing job records TestLiveHarnessReleaseFeeds/package/uv/tau-ai==0.4.7: https://pypi.org/pypi/tau-ai==0.4.7/json returned status 404, process exit 1. No product/source fix was authorized.
GitHub current base 36e0504a7e59239f7b9f083240104213d63e83aa, mergeable=false, mergeable_state=dirty. Recorded comparison main 474962e31bea34b96588e8d91ea7a46d82557f8c has 107 main-only / 26 PR-only commits versus tested head. No main merge or conflict-resolution operation was run.
Cleanup: PASS for owned teardown. Strict daemon PID 1488760 exited 0 and is absent; independent kernel-start was not captured before its default shutdown, so no stronger strict-process witness is claimed. API daemon identities: 1489380/161220784, 1490001/161225237, 1490567/161227155, each exited 0 and is absent. Native unprompted PID/kernel identity above is absent after bounded shutdown. Final scan found no remaining owned AO/native processes; no AO sessions remained, no UI process was launched, and no production process/service was changed. Parent still performs final owned-process verification/removal of only its clean detached worktree.
Private runtime retains strict report/artifacts, command/hash receipts, minimal isolated native config/session data, native-only bounded startup bytes, API receipts and binary, CI logs and an empty attachment-queue.json. None are Git evidence commits or public attachments. No credential stores, raw databases, profile directories or full terminal streams are published here.
Unresolved/next action: obtain approval for the existing matching provider credential route without resetting accounts; then establish an independent native provider/file witness and fresh AO preflight before any prerequisite-qualified diagnostic. Provision enough isolated desktop capacity, execute every applicable UI/model/provider/lifecycle journey, and attach real safe images through an approved uploader. Assess unfinished Chat/reviewer/setup controls independently, address the failing CI feed lookup/conflicts through an authorized coding owner, and rerun affected current-head qualification. Strict audit, provider authorization, exact restore, executing-tool cancellation, ordinary-task instruction consumption, full UI publication and full integration completion remain unverified.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Tau bounded current-head retest — BLOCKED, with CI FAIL. No full integration PASS.

Observed 2026-10-21T07:12:35.781155+00:00; Linux amd64. Tested/current PR head 16709897dc418ae265217b79d9fc0ffc9c389146 (fresh recheck 2026-10-21T07:11:02.570427+00:00); skill bfb28b79f90df0a56892e8d8b1d3139dea1148db. Every staged skill file matched that commit byte-for-byte. Source remained clean/detached; no source/branch changes, pushes, merges, review publication or evidence commits.

AO UI attachment evidence: BLOCKED. No actual Electron captures and no approved uploader. The full checkpoint index below is intentionally incomplete. PR-description link to this new evidence comment is pending parent action.

Runtime identity and actual attempts:

  • Native released CLI: tau 0.4.7; actual installed entrypoint SHA256 c2bb2a8b895236bb3789cd3420bd4ad986c366cdea91d3fb95ad155b996f7c7c. Original inventory launcher hash a85200514b8e0f1ffb3d7fa5724c68b87e173b7ae03cb50d6ed2e290e1461807 is a wrapper, not the underlying entrypoint. Fresh isolated credential-free launcher hash 26eb3c664c3182623475f0c8224ecdecbc70e5c84f7b9220fe90070b0d228048. Default metadata: provider zai-audit, kind openai-compatible, model glm-5.3-flash; effective authenticated routing is NOT_RUN.
  • AO: ao version dev, Go 1.27.1; executable SHA256 f0b8e56871e95d087b3e64b58386c8b0f89a8310de11144d16549a188cbff148. Embedded VCS revision equals tested head, vcs.modified=false. Serial go build -o /runtime/bin/ao ./cmd/ao: 2026-10-21T07:03:52.544443+00:00 → 2026-10-21T07:04:34.725536+00:00, exit 0. Limits: GOMAXPROCS=1, GOFLAGS=-p=1, GOMEMLIMIT=384MiB; Node 24.21.0 heap limit 384MiB. No routine local unit/race/lint/vet/typecheck/fixture/build-validation suites were run.
  • Fresh safe native --version, --help, providers, and exact TSV model projection all exited 0. Native and AO catalog count: 917, including zai-audit/glm-5.3-flash; this is local configured/catalog evidence, not 917 authorized models. Projection reads the actual 11-field native TSV and emits exact provider/model IDs; its private __audit-models dispatch is test plumbing, not an upstream flag.
  • strict-001: 2026-10-21T07:05:23.550137+00:00 → 2026-10-21T07:05:40.533164+00:00, exit 1, summary BLOCKED. Binary/version/integration/model probes, registration and installed gates PASS. First strict blocker: fresh_probe: readiness observations are not fresh. Probe HTTP 200 returned authStatus: unknown; readiness HTTP 200 returned auth unknown, freshness stale, checkedAt: null, auth_check_inconclusive, effective readiness unknown. AO catalog/lifecycle gates then NOT_RUN by strict policy. Report SHA256 f0ddd87632cbbcfe64d696d1c66fe4d5853c5fb1d175081ee73ba29330780158. No diagnostic runner attempt: mandatory native provider proof and fresh AO readiness prerequisites were unavailable.
  • Credential/provider witness: BLOCKED. The required provider key was absent from the worker environment. Automatic approval review rejected loading the existing matching provider key route. That rejection was not bypassed; credential content was not read/copied/printed, no login/account reset was attempted, and no provider turn was made. This is an operational authorization blocker, not a native credential rejection. Approval remains unanswered at this receipt. Independent native success has not been invented or used to upgrade AO auth.
  • api-001: OPERATOR/PROBE FAIL, retained. API off/on writes succeeded, then the private helper raised KeyError: harnessDefaults because empty preferences are omitted. Exact owned daemon shut down exit 0. No product fix. api-002: limited API PASS for 917-model catalog/refresh, off/on and bulk save/readback, and persisted disabled model after an owned daemon restart. This supplies no actual picker/UI/effective-provider proof. Explicit Chat create returned 409 SESSION_MODE_UNSUPPORTED: tau has no chat driver; subsequent session inventory was empty. Negative reviewer request against a nonexistent scratch session returned 500 REVIEW_OPERATION_FAILED; this is preserved and does not prove supported reviewer behavior or a truthful reviewer-capability rejection.
  • native-safe-001: unprompted real native TUI startup observed Ask Tau…, then intentionally SIGTERM/reaped (exit -15), no task/provider call. PID 1490665/kernel-start 161231190; raw bounded native stream retained privately, not presented as AO UI. Native --mode acp exited 2 before provider execution; help/source expose Pi-compatible RPC rather than ACP. Fresh startup is not restored/empty-composer proof; no restoredReady regex was fabricated.
  • Desktop preflight BLOCKED: frontend dependencies absent; 1,497 lockfile packages. Free disk was 846MiB, only 146MiB above the required 700MiB floor. Official pinned Electron 33.4.11 archive measured 106,366,319 compressed bytes and 274,653,350 unpacked bytes (261.93MiB) across 74 entries, before npm dependencies. Archive directory was measured by a streamed read without disk writes after Range metadata failed HTTP 501. npm ci and actual Electron launch NOT_RUN to preserve the floor; no old source/dependency tree/screenshot was reused. All captures and attachments unavailable. Final measured free disk at cleanup: 832MiB.
    Reproduction receipt (paths normalized; no credential-store/profile paths or values published):
GOMAXPROCS=1 GOFLAGS=-p=1 GOMEMLIMIT=384MiB go build -o /runtime/bin/ao ./cmd/ao
# Use the isolated native launcher and minimal copied configuration; do not load a denied key route.
TMPDIR=/runtime/tmp PATH=/runtime/bin:$PATH NODE_OPTIONS=--max-old-space-size=384 \
node /pinned-skill/scripts/audit_ao.mjs --agent tau --repo /clean-tested-source \
  --ao /runtime/bin/ao --local-contract /runtime/contract-strict.json \
  --report /runtime/attempts/strict-001/report --startup-timeout-seconds 60 --timeout-seconds 30

Contract original-byte SHA256 1ed9c270abc07ec8d9a7e1ffda16c621a64dae255c89f23399ffda69e21f6b07; path-normalized content below (path normalization changes bytes/hash). session deliberately absent because credential loading was denied; native source-derived intended safe session args are --print --approve --mode json {prompt}, never executed. restoredReady absent because fresh startup/settled/draft/restored matching samples are missing. Escape derives from pinned native binding. Profiles were limited to known provider/catalog config copies, mode 0700/0600.

{
  "schemaVersion": 1,
  "agents": {
    "tau": {
      "binary": "/runtime/bin/tau",
      "versionArgs": [
        "--version"
      ],
      "integration": {
        "args": [
          "providers"
        ],
        "expect": "zai-audit"
      },
      "models": {
        "args": [
          "__audit-models"
        ],
        "format": "json"
      },
      "aoModelsPath": "agents/{agent}/models",
      "interrupt": {
        "input": "<single ESC byte 0x1b>",
        "settleTimeoutMs": 5000
      }
    }
  }
}

Completion matrix:

Area Supported scope Verification Proof or reason
Registration and UI Registered Tau TUI, API/DTO/product identity; actual desktop BLOCKED API registered/installed PASS. Actual Agent Harness and New Task UI unavailable because fresh Electron cannot fit above the disk floor.
Models Native configured catalog and both AO model surfaces BLOCKED Native and AO each expose 917 exact provider/model IDs; refresh and off/on/bulk API readback plus daemon-restart persistence PASS. Both UI surfaces, picker effects and effective launched selection NOT_RUN.
Providers Explicit native provider metadata and account/routing controls BLOCKED Native TSV identifies default zai-audit, OpenAI-compatible kind, glm-5.3-flash, and required key name. Credential source approval rejected; effective routing/provider turn NOT_RUN. AO add/edit/remove/account UI not exercised.
Setup AO installer and Account setup/error/retry NOT_RUN Display-safe plans read: uv tool install tau-ai==0.4.7 and documentation-only /login guidance. Installs/upgrades/login/account changes prohibited; no install/setup action executed. CI release-feed lookup fails 404.
Readiness Installed Tau 0.4.7 on Linux; native and AO readiness BLOCKED Strict fresh_probe BLOCKED: authentication unknown/stale, auth_check_inconclusive, no checkedAt. Native unprompted Ask Tau cue observed, but no verified provider authorization. Existing matching key was not inherited; automatic approval rejected loading it.
Identity and logo Tau product label/avatar BLOCKED Product label Tau registered; current AgentAvatar has no Tau asset and falls back to an initial. Native UI branding/license verification unavailable; fallback intent is not documented here.
TUI and Chat TUI; independently assessed ACP/shared Chat BLOCKED Unprompted native TUI startup PASS only. Strict AO turns NOT_RUN. Native --mode acp rejects with exit 2; installed CLI/source offers Pi-compatible RPC, not ACP. AO Chat is unregistered and explicit request returns 409 SESSION_MODE_UNSUPPORTED; broader RPC Chat wiring NOT_IMPLEMENTED.
Reviewer Separate AO reviewer registry, pane, run/result/cancel/rerun NOT_RUN Tau is absent from reviewer registry/DTO. No native special reviewer capability qualified; headless prompt mode exists but suitability/wiring unfinished. Negative request against nonexistent scratch session returned generic 500, not a successful capability rejection. No GitHub review/publication executed; publication prohibited.
Permissions and instructions Explicit bypass only; additive standing/project instructions NOT_RUN Source rejects default, accept-edits, auto and allow/deny restrictions; native Escape binding confirmed. No authenticated AO turn, effective permission behavior, independent instructions or restored fresh token consumption qualified.
Lifecycle Active-tool cancel, Kill/archive, exact restore, Kanban, reconnect NOT_RUN Strict prerequisite blocked all dependent turns. No executing-command PID/kernel witness, delayed-side-effect check, provider history/restore or continuation. API preference persistence across daemon restart is not native session recovery.
Evidence Current build, distinct attempts, UI checkpoint publication BLOCKED Strict and independent receipts retained outside Git; 24 required screenshot rows retained plus Chat/reviewer subjourneys. Zero actual Electron captures. AO UI attachment evidence: BLOCKED; no approved uploader and private queue is empty.
CI and handoff Current-head remote checks, conflicts, cleanup and parent handoff FAIL 26 completed check runs: 25 success, live-feeds failure (Tau pinned package PyPI URL 404). Legacy combined status says pending with zero contexts; no pending check-run job observed. PR mergeable=false/dirty. Owned processes gone; source clean. PR-description evidence link pending parent.
Screenshot checkpoint index, created before actions. Shared provenance: tested frontend/source head above; actual desktop never launched, so capture time/session/generation/image hashes and attachment URLs do not exist. Every capture is unavailable; no private PNG counts as published proof.
Checkpoint/substep Action → observed result Functional status Screenshot/attachment
--- --- --- ---
harness-listed Open Agent Harness → no actual Electron surface BLOCKED BLOCKED: unavailable
install-offer Inspect install action → no UI; API advertises uv pinned install BLOCKED BLOCKED: unavailable
install-run Start/progress/result → not started NOT_RUN BLOCKED: unavailable
auth-before Inspect existing account → no UI; AO unknown/stale BLOCKED BLOCKED: unavailable
auth-action Start Login/Setup and return → not started NOT_RUN BLOCKED: unavailable
auth-ready Fresh verify and provider turn → no turn BLOCKED BLOCKED: unavailable
auth-maintenance Change/logout/retry → not acted NOT_RUN BLOCKED: unavailable
harness-models List/refresh → 917 API models; UI unavailable BLOCKED BLOCKED: unavailable
model-visibility Off/on/bulk/save/reload/pickers → API persistence PASS only BLOCKED BLOCKED: unavailable
provider-management Browse/configure/switch provider → metadata read only BLOCKED BLOCKED: unavailable
task-agent Board New Task → not opened BLOCKED BLOCKED: unavailable
task-model Choose model → no UI selection/launch BLOCKED BLOCKED: unavailable
task-running Submit/card/initial output/settle → not submitted NOT_RUN BLOCKED: unavailable
task-followup Normal composer follow-up → not sent NOT_RUN BLOCKED: unavailable
task-cancel Executing tool/Stop/settle → not started NOT_RUN BLOCKED: unavailable
kill-action Archive control/confirm/terminated → not acted NOT_RUN BLOCKED: unavailable
archived Show exact archived entry → no entry NOT_RUN BLOCKED: unavailable
restore-action Restore exact history/empty composer → not acted NOT_RUN BLOCKED: unavailable
kanban-return Same restored card/continuation → not acted NOT_RUN BLOCKED: unavailable
chat Shared New Task/composer/stream/approval/Stop/recovery → not run NOT_RUN BLOCKED: unavailable
reviewer-select Select Tau reviewer/target 6493 at tested head → unavailable NOT_RUN BLOCKED: unavailable
reviewer-running Review/run/cancel/error/retry → no execution NOT_RUN BLOCKED: unavailable
reviewer-result Result/verdict/rerun → no result NOT_RUN BLOCKED: unavailable
reconnect-cleanup UI reconnect/recovery/final cleanup → no UI BLOCKED BLOCKED: unavailable
chat/new-task Not exercised NOT_RUN BLOCKED: unavailable
chat/followup-stream Not exercised NOT_RUN BLOCKED: unavailable
chat/load-history Not exercised NOT_RUN BLOCKED: unavailable
chat/approve Not exercised NOT_RUN BLOCKED: unavailable
chat/reject Not exercised NOT_RUN BLOCKED: unavailable
chat/cancel-active-tool Not exercised NOT_RUN BLOCKED: unavailable
chat/ui-reconnect Not exercised NOT_RUN BLOCKED: unavailable
chat/daemon-host-recovery Not exercised NOT_RUN BLOCKED: unavailable
chat/kill-restore-instructions Not exercised NOT_RUN BLOCKED: unavailable
chat/negative-restore-capabilities Not exercised NOT_RUN BLOCKED: unavailable
reviewer/target-head Not exercised NOT_RUN BLOCKED: unavailable
reviewer/run Not exercised NOT_RUN BLOCKED: unavailable
reviewer/result Not exercised NOT_RUN BLOCKED: unavailable
reviewer/cancel Not exercised NOT_RUN BLOCKED: unavailable
reviewer/rerun Not exercised NOT_RUN BLOCKED: unavailable
Current-head CI, read from GitHub (no local routine validation). The check runs refer to this exact implementation head and were completed on 15 October; reading them today is not a new CI rerun. released-tui is a localhost fixture-provider contract test, not authenticated external-provider proof. No pending/failing job is hidden below. Legacy combined status endpoint separately reports pending with an empty status-context list.
Check Current-head state Proof
--- --- ---
build-test completed / success job
native (windows-latest) completed / success job
native (ubuntu-latest) completed / success job
native (macos-latest) completed / success job
container completed / success job
sqlite-race (2) completed / success job
lint completed / success job
sqlite-race (1) completed / success job
sqlc-drift completed / success job
windows-workspace completed / success job
cloud-build-test completed / success job
session-store-race completed / success job
released-tui completed / success job
backend-core (0) completed / success job
chat-race (1) completed / success job
api-drift completed / success job
sqlite-race (3) completed / success job
backend-core (1) completed / success job
sqlite-race (0) completed / success job
test completed / success job
mac-update-helper completed / success job
chat-race (0) completed / success job
linux-proof-artifact completed / success job
scan completed / success job
live-feeds completed / failure job
renderer-smoke completed / success job
The failing job records TestLiveHarnessReleaseFeeds/package/uv/tau-ai==0.4.7: https://pypi.org/pypi/tau-ai==0.4.7/json returned status 404, process exit 1. No product/source fix was authorized.
GitHub current base 36e0504a7e59239f7b9f083240104213d63e83aa, mergeable=false, mergeable_state=dirty. Recorded comparison main 474962e31bea34b96588e8d91ea7a46d82557f8c has 107 main-only / 26 PR-only commits versus tested head. No main merge or conflict-resolution operation was run.
Cleanup: PASS for owned teardown. Strict daemon PID 1488760 exited 0 and is absent; independent kernel-start was not captured before its default shutdown, so no stronger strict-process witness is claimed. API daemon identities: 1489380/161220784, 1490001/161225237, 1490567/161227155, each exited 0 and is absent. Native unprompted PID/kernel identity above is absent after bounded shutdown. Final scan found no remaining owned AO/native processes; no AO sessions remained, no UI process was launched, and no production process/service was changed. Parent still performs final owned-process verification/removal of only its clean detached worktree.
Private runtime retains strict report/artifacts, command/hash receipts, minimal isolated native config/session data, native-only bounded startup bytes, API receipts and binary, CI logs and an empty attachment-queue.json. None are Git evidence commits or public attachments. No credential stores, raw databases, profile directories or full terminal streams are published here.
Unresolved/next action: obtain approval for the existing matching provider credential route without resetting accounts; then establish an independent native provider/file witness and fresh AO preflight before any prerequisite-qualified diagnostic. Provision enough isolated desktop capacity, execute every applicable UI/model/provider/lifecycle journey, and attach real safe images through an approved uploader. Assess unfinished Chat/reviewer/setup controls independently, address the failing CI feed lookup/conflicts through an authorized coding owner, and rerun affected current-head qualification. Strict audit, provider authorization, exact restore, executing-tool cancellation, ordinary-task instruction consumption, full UI publication and full integration completion remain unverified.

Publication receipt: the earlier new evidence comment is retained intact. Its readback transformed the textual Unicode Escape sequence in the contract snippet. This final comment describes the byte symbolically: construct the actual runtime interrupt.input value with String.fromCharCode(27) before JSON serialization. The symbolic snippet is explanatory, not directly executable JSON configuration. Actual retained contract bytes/hash and the strict failure above are unchanged. No old comment was edited or deleted.

nikhilachale and others added 5 commits October 21, 2026 22:03
Tau's Account row only offered View documentation. Open tau and inject
/login once the composer renders, which opens Tau's native login-method
picker (subscription OAuth, API key, or custom provider).

Add Tau's official mark (white tau on black, from twotimespi.dev) so
session and harness surfaces stop falling back to a lettered tile.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tau sessions failed to spawn under AO's default permission mode because
the adapter rejected anything but bypass-permissions. Tau has no tool
approval policy or permission flags, so handle it like Pi: emit no
permission flag for any mode and defer to Tau's own behavior.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The adapter accepted exactly tau-ai 0.4.7, so any upgrade, including
AO's own managed update to 0.4.8, made every Tau launch fail. Treat
0.4.7 as a minimum in launch, restore and ao doctor through one
tau.CheckVersion, and install the latest tau-ai.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nikhilachale

Copy link
Copy Markdown
Collaborator Author
Screenshot 2026-10-22 at 00 55 09

@nikhilachale
nikhilachale marked this pull request as ready for review October 21, 2026 19:32
List codewhale and tau in ao spawn --harness help, and declare Tau's
terminal version refresh capability (unsupported: restore needs native
history and is not yet audited for unattended resume).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@milesatao-svg milesatao-svg mentioned this pull request Nov 12, 2026
2 of 4 tasks
@milesatao-svg

Copy link
Copy Markdown
Contributor

Continuation under the new contributor account

This harness submission has been copied to PR #8210 under @milesatao-svg as part of the contributor's account migration.

The replacement draft preserves source head f0161ed2151383a6e814347e81f83b5c591834e4, commit authorship, the original description, and historical evidence with source attribution. Published copy verification is recorded in this comment. Fresh CI and current mergeability are tracked on the replacement PR.

@nikhilachale

Copy link
Copy Markdown
Collaborator Author

Closing this original harness submission as superseded by PR #8210 under my new contributor account @milesatao-svg.

Copy verification confirmed the same original head f0161ed2151383a6e814347e81f83b5c591834e4, the description, change-count header, and all original human comment content and media references.

The replacement is a draft. Main merge conflicts and fresh CI validation are pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/daemon Go daemon, process lifecycle, and backend control plane. enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants