Skip to content

Releases

0x2F 1.1.0 — review context before continuing

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 15 Nov 20:05
c07b3bf

Review the context before continuing a task through the same or another coding agent.

Local Web and TUI now open a next-run preview before correction, answer-and-continue, retry and reopen. Inspect instructions, prior-result delivery and the exact task prompt, select a harness, then explicitly start. Cancellation returns to the draft. Stale reviews refuse before a new run starts; lost responses reconcile task state without automatically retrying execution.

CLI adds 2f preview <id> [--provider <id>] and guarded 2f rerun <id> --preview <preview-id>. Existing direct reruns remain available. No task-data migration is introduced. Phone companion and operator self-hosting remain experimental; full preview is local.

npm install -g 0x2f@1.1.0
2f version

Release guide and upgrade/rollback · Preview guide · Exact qualification · Website

Validation: both GitHub workflows passed six macOS/Linux Node 20/24/26 jobs and the separate Caddy loopback job. Exact archive installations pass CLI, real TUI and detached-worker continuation on both workstation hosts, including empty-HOME verification. A synthetic upgrade from public 1.0.0 preserves workspace file bytes. Skipped vendor binaries and support limits are documented in the qualification record.

Archive SHA256: 39ee39b9c7d1f6f892a373da08af0f5b514bc68c648ac24d8d08795fd0a31ef4.

Publication verified: npm latest is 1.1.0; ordinary public installations pass on macOS and Linux. The website and documentation at 0x2f.space are live. The attached publication-receipt.json records exact registry, GitHub, CI and production-site checks.

0x2F 1.0.0

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 15 Nov 13:06
51c96cb

0x2F’s first stable release: persistent tasks across sequential runs and supported coding harnesses, with clear results and an explicit next action.

  • Compact Web results, distinct headings and green commands; clearer dark and light TUI layouts.
  • Grapheme-safe terminal editing, visual arrow movement across wrapped lines, and reliable draft recovery at narrow sizes.
  • Stronger remote authorization and persisted replay admission, separate workspace browser authentication, safer Linux recovery and terminal output.
  • Approved screenshots show real Codex tasks, recorded activity and progress based on the task’s previous run.

Install:

npm install -g 0x2f@1.0.0
2f version

The qualified core is local CLI, TUI and desktop Web on macOS arm64 and Linux x86_64, with Node.js ≥20 and an installed, authenticated supported harness. Phone companion and operator self-hosting remain experimental. Final physical-phone/background-return checks were not run because the device was unavailable. No operated public relay service is included.

Verification: six complete macOS/Linux suites on Node 20.20.2, 24.22.3 and 26.13.1; separate-prefix and empty-HOME/offline installs; installed PTY reading and 37 structural frames; static assets; upgrade from public 0.3.0 with all 14 task files unchanged. Actual GitHub CI and registry checks are recorded in the qualification document.

Archive SHA256:

9ee1d61be7ee906014d536554adce3db75842742d0c14a2ec6572543fe2d90d9  0x2f-1.0.0.tgz

Release scope, upgrade and rollback · Exact qualification and limits · Documentation

0x2F 0.3.0

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 02 Nov 22:58

0x2F0.3.0 — release scope and upgrade

Release date:2026-11-02. npm 0x2f@0.3.0, tag v0.3.0.
Local work routing for macOS and Linux/POSIX, Node.js≥20. Current platform
verification uses macOS arm64/Node26.11.1 and Ubuntu26.04.1 x86_64/Node26.13.0.

Changes since published0.2.0

  • CANCEL targets the current execution occurrence, waits for the owned process
    group and preserves partial artifacts. Recovery distinguishes dead/mismatched
    process identity; saved numeric PIDs do not grant future signaling authority.
  • Git task worktrees separate executions from the original checkout. Immutable
    snapshots and saved patches support review and explicit apply. Archive/restore
    retain unfinished bytes; cleanup refuses unsupported ignored/index/reserved
    states instead of deleting data. Shared mode still permits external writers.
  • Project-configured checks freeze argv/timeout plans before launch and retain
    actual output hashes and exit receipts. They execute as the host OS user,
    outside provider sandboxing. READY/check success is separate from human ACCEPT.
  • Exact per-attempt input/context receipts retain notes, current rules, decisions
    and earlier results within explicit size limits. Tool evidence stays bound to
    its execution. Fresh-session continuation differs from native provider resume.
  • Explicit Linux remote-host commands use strict known hosts and recheck the
    pinned machine identity on the actual execution connection. The work executes
    on that host; tasks, dirty files and credentials are not migrated between hosts.
  • Quiescent private backup retains a self-contained workspace, Git and task state;
    integrity-checked restore uses a new root and disables execution/replay authority,
    relay credentials and host profiles. It does not automatically launch work.
  • Web/mobile surfaces add task creation, correction and occurrence-bound CANCEL;
    refused/ambiguous mutations preserve draft or require inspection. TUI/Web review
    exposes saved runs, input, changes and independent check evidence.
    -057 may observe0x2F externally through its opt-in engineering reader. No057 Core,
    renderer or Mobile public application is bundled or publicly upgraded by0.3.0.

Commands and precise authority boundaries.

Qualification linkage

Historical independent qualification used source checkpoint
839e980dd20db3ea058ef4abc707ceeb322a0e93 and candidate tarball0x2f-0.2.0.tgz, SHA256
4aa0dd547bf3245a78acca09133ecf070a48fc74e3cc5d5afff74e5270250626.
That candidate differs from published registry0.2.0. Its reports are not relabelled
as0.3.0 tests. On those bytes, Mac821tests and Linux811tests/10explicit skips,
installed69critical/83encrypted contracts per platform, and a full real Linux
Codex0.166.0/openai/gpt-6.1-sol two-run/check/restart/backup/restore loop passed.

The0.3.0 artifact comparison permits only package/ACP client version metadata
and current README release text. All other packaged product files must match
that candidate byte for byte. Fresh source regression/build and exact installed
package contracts/smokes are recorded in the 0.3.0 release checkpoint. The proven
AI loop is linked through unchanged behavior, without repeating paid/live models.

Upgrade and rollback

  1. Quiesce old workers and other writers; inspect active tasks before service stop.
  2. Preserve the previous prefix, service configuration and a consistent private
    workspace/state backup. Backups can contain secrets; retain owner-only access.
  3. Install the published0.3.0 into a separate prefix, verify it, then update the
    normal launcher/service during quiescence. Preserve pairing, machine identity,
    enabled/linger state, settings and provider defaults.
  4. Keep a matching0.3.0 executable for new isolated tasks. Old0.2.0 does not own
    their checkout/execution contracts and must not execute them against source.
  5. For rollback, quiesce the new runtime and restore the matching prior prefix
    and consistent old state, retaining newer evidence. Restored work has no live
    credentials/host/execution authority; configure trust deliberately afterward.

Limits and deferred work

Worktrees/check environments are not OS sandbox containment. Escaped process
groups, universal per-harness permission/resume/cancel parity, acknowledged live
steering, closed-client push, independent phone registrations, host-to-host task
migration, cold reboot/production rollback drills and long-duration thermal/pixel
behavior are not newly qualified. Mobile interruption/runtime-error recovery
remains UNVERIFIED in a separate owner-approved follow-up; it is not a0x2F gate.
No App Store/notarized057/Mobile distribution is part of this release.

Release artifact verification

Release commit: 33a09878a3f7c941771265e6d1f865cb1aee06f6.

SHA-256: 7cf66322908f446fcd777c62664b425e000a9a752e50d8cbc3e5e84f4285c1be.

Fresh source regression: 821 passed; syntax and client build passed. Exact installed package on Mac and Lenovo: 120 critical/ACP, 73 encrypted remote, 117 CLI/TUI/Web tests per platform; two-run/check/restart/backup/restore fixture and HTTP/CLI reopen smoke passed. Real AI qualification remains explicitly linked to the historical candidate through unchanged behavioral bytes.

Install: npm install -g 0x2f@0.3.0.

0x2f v0.2.0

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 02 Nov 10:39
ecf547c

0x2F 0.2.0

0x2F keeps a Task across harness runs: the original request, constraints, decisions, exact run inputs and saved results. 0.2.0 adds faithful review and qualifies one persistent Linux execution host controlled from Mac and phone.

  • Hardened runtime locking/concurrency, occurrence-bound permissions and retry recovery. systemd restart preserves detached workers; supervised LAN pairing no longer starts a competing runtime.
  • Full TUI reader for request, result, reported Verification and exact input; saved notes reach the next run. READY remains a review result. CLOSE does not cancel a provider.
  • Added Web/mobile/pairing Light / Dark / System with saved preference and pre-paint resolution, preserving the original Light design and existing TUI theme selection. Responsive headers, long results and activity lanes no longer crop their final marker. README screenshots show the current Dark interface with explicitly illustrative data.
  • Portable verifier with explicit public cache, clean HOME/PATH, no inherited credentials, offline installation and byte-for-byte package checks.
  • Updated quickstart, commands, host setup, troubleshooting, compatibility and roadmap. Historical qualifications retain their original versions/dates, including the real Codex → Cursor → Codex handoff.

Install with Node.js ≥20:

npm install -g 0x2f@0.2.0
2f version

Final validation: 783/783 normal regression; each isolated macOS/Linux suite passed 773 with 10 explicit native-CLI skips; exact canonical tarball installed on Linux with all 77 package files matched and CLI/reader-PTY/Web checks passed; 12/12 real-PTY visual frames passed. Light/Dark responsive geometry and long-result checks passed. Two real OpenCode 2.2.5 runs on Lenovo retained task history, saved constraint, files and results across closed clients and service restart; physical iPhone control and the existing 057 Display/MACHINE PULSE path were checked separately.

Boundaries: one local runtime/workspace on Linux, no task migration/fleet/failover; no project-operated Internet relay; no general Windows qualification. Cursor native resume and interactive permissions were not exercised in its recorded live handoff. Aggregate CPU does not prove per-agent activity. This is not a new 057 release or full visual/thermal/overnight qualification. No Lenovo reboot test or additional paid benchmark is claimed. 1.0 is deferred.

Full verification and limitations · Quickstart · Compatibility · Host setup · Site

Canonical package SHA256: eb4d9dd9fc43873ca66906b9d06827459192d94b4e75f65636d7ff37563a1fba.

0x2f v0.1.4

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 31 Oct 19:25

0x2F 0.1.4

  • Task creation prints the persisted Task ID and its exact 2f open <id>
    command. Reopen Tasks from another process and inspect individual runs;
    incomplete --run selections now report a usage error.
  • Continue the same Task through another harness with
    2f rerun <id> --provider <provider>. Prior results, decisions, and evidence
    remain available through persisted Task context. One real Codex → OpenCode
    engineering correction has been verified without a manual handoff.
  • OpenCode is built in through the existing ACP integration (opencode acp);
    an installed OpenCode CLI and an available, configured model are required.
  • Set CODEX_IGNORE_USER_CONFIG=1 to use Codex's account default instead of
    unsupported user-config overrides. Existing authentication is preserved;
    ordinary Codex configuration remains unchanged unless this option is set.

CLI, TUI, and Web continue to use the same durable Task state. This release
does not include the experimental managed Responses lane or change scheduler,
credentials, or unattended-execution policy.

The continuity observation concerns a new run on the same Task through a new
harness session; it does not imply resuming the original provider session.

0x2f v0.1.3

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 01 Sep 18:41

0.1.3 — provenance alignment

Published to the npm registry as 0x2f@0.1.3. Propagates the PROBNAYA identity and repository transfer to npm — no runtime behavior changes.

Changes

  • PROBNAYA identity — README now opens with the PROBNAYA / 0x2F header and Independent Computational Laboratory attribution
  • Repository provenance — repository, bugs, and homepage fields in package.json now point to probnaya-work/0x2f and 0x2f.space; no stale AleksandrMalinin/0x2f references remain
  • License and legal attribution — MIT, Aleksandr Malinin, unchanged

Install

npm install -g 0x2f        # the 2f command lands on your PATH

Install: 0x2f on npm · Docs: 0x2f.space

0x2f v0.1.2

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 29 Aug 13:50

0.1.2 — release-readiness fixes

Published to the npm registry as 0x2f@0.1.2. Fixes the concrete correctness blockers surfaced by a public dogfood across Claude Code, Codex and DeepSeek Harness, plus host-reliability work and two TUI fixes.

Changes

  • Claude permission continuation — 2f allow now fails honestly (failure.kind: "resume") when Claude Code's print-mode session resume is unavailable, instead of pretending the granted work continued
  • Remote actions from the phone — ACCEPT / ANSWER / ALLOW / REJECT / SEND BACK settle within a bound and reconcile with the Mac's authoritative state, never leaving the phone pending or stale
  • Changed-file counts — provider-reported and repository-observed file changes are canonicalized and deduplicated, with the observed final state authoritative — phone, TUI and Web now agree
  • Release identity — 2f --version / 2f -v / 2f version report the package version
  • Host reliability — atomic task persistence; a startup recovery sweep for interrupted runs; a foreground runtime entry with graceful shutdown and launchd/systemd units (2f serve)
  • TUI — fixed the 256-color cube quantization off-by-one; added an outer gutter so the frame never sits flush against the edge
  • Docs — routing.json documented as optional and hand-authored; README updates

Install

npm install -g 0x2f        # the 2f command lands on your PATH

Install: 0x2f on npm · Docs: 0x2f.space

0x2f v0.1.1

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 28 Aug 21:38

0.1.1 — consistency patch

Published to the npm registry as 0x2f@0.1.1. This is a documentation/source consistency patch, not a behavior change.

Changes

  • Version bumped to 0.1.1
  • ACP clientInfo.version corrected from the stale pre-release 0.4.0 to 0.1.1
  • Stale pre-release references (v0.5 / v0.6) removed from src/, docs, deploy and relay READMEs — the product had never shipped publicly under those internal numbers
  • Hosted-relay default-flow description corrected (plain 2f pair pairs over the local network; the hosted endpoints are used with --relay/--client or the env vars)
  • Cursor ACP manifest example aligned with the verified example in examples/providers/

Install

npm install -g 0x2f        # the 2f command lands on your PATH

Install: 0x2f on npm · Docs: 0x2f.space

0x2f v0.1.0

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 27 Aug 23:41

First public release

0x2f is a task-native wrapper around coding agents: give it engineering work and it routes the task to a coding harness on your machine, runs it in the background, and tracks it through the lifecycle.

Install (Node.js ≥ 20):

npm install -g 0x2f        # the 2f command lands on your PATH

Published to the npm registry as 0x2f@0.1.0.

Highlights

  • Task-native model — the task, not the agent session, is the persistent unit of work; runs are disposable executions underneath it
  • Providers — built-in Claude Code, Codex, DeepSeek Harness, Gemini CLI, plus ACP-compatible agents and headless command providers per project
  • Surfaces — 2f CLI, 2f tui terminal client, 2f ui local-first Web UI, and phone remote control via 2f pair (end-to-end encrypted)
  • Work lifecycle — permission and decision blocks, run history with reruns, notes/corrections carried into the next run, event-sourced state in .work/
  • Local-first & minimal — one runtime dependency (ws), no build step, no accounts, no daemon

Checks

  • Distribution/security/package test suite green (45/45 release set; 574/574 non-PTY suite)
  • npm audit: 0 vulnerabilities
  • Packed artifact verified: 67 files, 254.9 kB, 2f bin from npm install -g 0x2f