ISyCode is version 0.1.0 in active development. A product-oriented README does not change release acceptance, security gates or integration evidence. This page keeps those limits visible without making the landing page an audit log.
On 2026-10-12, a fresh clone of public main installed on Linux in a new virtual
environment; isycode --version and --help exited successfully. The current
local Textual source rendered the Overview, populated Files and grouped
Settings captures in an isolated demo workspace. File listing/preview used
the actual read owner and verified local receipts. No model inference, Gateway,
MCP tool or clipboard backend ran for those captures.
Commands, outputs, inspected remote metadata and hashes are in the GitHub/documentation audit. This task did not rerun the global application suite or certify another OS.
The completed native menu integration records the primary-main source, native captures at three terminal sizes, independent review, full hermetic-suite runs, real installed-command PTY startup and isolated wheel checks. Raw failures remain preserved alongside the later verification. Its Spanish guide explains the current menu and text gestures.
The historical G8 manifest was restored byte-for-byte to the originally reviewed version after an independent provenance review. That correction does not approve the current source or a release: the current strict validator still rejects the M8 source associations. Details and negative results are in the integration report. The earlier TUI implementation report remains a dated record of its original attempts and limits.
Physical-terminal mouse/clipboard roundtrip after the new gestures, terminal font fallback, live services and release acceptance were NOT_DEMONSTRATED by that implementation report. Textual SVG font rendering is not a terminal font-setting test.
The platform parity report records native Windows storage, ownership/DACL, process/thread exclusion, iteration/session recovery, approved edits and Git workflow tests, plus Linux container regression runs. The provider in the coding-flow test is simulated; filesystem/Git owners and their receipts are real. The PowerShell source installer is also verified. This evidence narrows the pending native Windows scope below; full product parity, native Windows command isolation, live inference, physical clipboard and packaged EXE behavior remain NOT_DEMONSTRATED.
These are dated records referenced by the previous README, not new runs in this task. Inspect the original commands and hashes before making a current claim.
| Scope | Evidence location |
|---|---|
| Continuity capsule/recovery with NVIDIA NIM, 2026-10-08 | Canary evidence |
| Local context7 server with approved/rejected calls; model simulated, 2026-10-08 | MCP evidence |
| RTK compression/original output retrieval | RTK guide and evidence |
| Broader daily-use scope, sandbox, clipboard and provider witnesses | Daily-use readiness |
| Historical product feature matrix, 2026-09-28 | Feature matrix |
The old README also reported NVIDIA coding/streaming, Pyright/TypeScript handshakes, X11 clipboard and bubblewrap runs, plus a local Docker broker. Their exact historical wording is retained in the archived README. They were not re-executed here and are not an all-provider/platform guarantee.
- Live Gateway semantic operations with matching permission, scope and IDs; deployment HTTPS witnesses and M15 remote coverage.
- Real tailnet/Mobile Host sessions, streaming and approvals.
- Native Anthropic inference and native Windows product workflows.
- Recovery across providers, live 429/5xx behavior and prompt-cache savings.
- Real-page Playwright snapshot sharing with human review and evaluated fidelity.
- LSP behavior beyond the individually recorded handshake/diagnostic scope.
- Recursive directory/binary/large-file mutation beyond documented owner limits.
- Adversarial/dogfood/performance acceptance and gradual release milestones.
The Classic/Security roadmap and product roadmap track acceptance. The previous README's broad M0–M8 approval sentence must not be read as approving the current source or a new release. No installer release was published when the repository was inspected on 2026-10-12.