Autark 0.3.3

Autark 0.3.3 – the last release in this repository.

Autark has moved to teydra/OpenAutark. This release holds the same files, byte for byte, as 0.3.3 there (plus the three packages once more under their old workforce-* names, for the download button of older versions), so every installed Autark up to 0.3.2 finds it here and updates as usual. From 0.3.3 on, the app looks for updates only in OpenAutark; new downloads are there too:

• Windows: https://github.com/teydra/OpenAutark/releases/latest/download/autark-windows-x64.exe
• Mac: https://github.com/teydra/OpenAutark/releases/latest/download/autark-mac-universal.dmg
• Linux: https://github.com/teydra/OpenAutark/releases/latest/download/autark-linux-x64.AppImage
• Android: https://github.com/teydra/OpenAutark/releases/latest/download/autark-android.apk

The first update to 0.3.3 downloads the full installer once (about 130 MB on Windows). The old download names workforce-* are carried here one last time; OpenAutark has only autark-*.

New since 0.3.2:

• Updates reopen by themselves: on Windows and Linux a small helper waits until Autark has closed, installs the new version and starts it again; before the window closes, Autark says "Autark is installing 0.3.3 and opens again by itself in about a minute". The installer no longer starts PowerShell to look for a running app, so the gap is shorter. Each step writes one line to update-helper.log in the log folder.
• Your devices have no roles any more: connecting your other PC mirrors everything. Joining a company as an employee is its own entry in the new "+" menu.
• The phone belongs to the company: pair it with your PC's Remote ID; both screens show the same code and you accept on the PC. Notifications reach every phone, and reading on one device marks it read everywhere.
• iPhone without an App Store app: a web app (Share › Add to Home Screen) that connects through the meeting server, end to end encrypted.
• Android phone use: agents can operate the phone through an accessibility service you switch on once; a bubble on screen stops it.
• Chats: a 1:1 stays between two; sub-chats and threads for side topics.
• Questions are quick replies: important ones stay in a strip above the composer; My day lists only what needs your hands.
• Work: big "For you" cards plus a short report of side work and interesting facts.
• One knowledge system: memory, skills, your project's instruction files and the public library, searched together.
• Personal manager: your first agent is your right hand and head of staff; it can look at other people's calendars and book across PCs, and fill a login in the built-in browser.
• Models and settings: real prices and a smartness score per model; the Voice page merged into Models; fewer, clearer settings; the plan rail shows a ring with the 5-hour window.
• More work at once: how many heavy agent turns run together now follows the real free memory (on our 8 GB test PC 5 instead of 1).
• Android: autark-android.apk, signed with Autark's release key. A phone with the earlier preview build uninstalls that once. The app offers later versions itself (latest-android.json).

Verification: on the release snapshot, typecheck 0 errors, import boundaries ok, build ok, 5,275 unit tests (5,271 passed, 3 skipped, 1 timing test of the Linux pointer path that is flaky on a loaded Windows PC and passed on rerun), 24 end-to-end and 4 window tests passed, Electron smoke passed. The CI runners checked the packaged app natively on Windows x64, Linux x64, macOS Apple silicon and macOS Intel (version, 220 build files, SQLite, speech addon, runtime RPC, demo chat, first window without renderer errors). Local update test on Windows: the installed app downloaded only the changed parts (13 MB of 132 MB) and was back as 0.3.3 85 s after "Restart", with all agents, chats, tasks and secrets.

Windows and Linux update in the app. The Mac app replaces itself where macOS allows it; that path has not yet run on a real Mac. The Mac package is ad-hoc signed, without Apple Developer ID or notarization; Windows remains unsigned. Not established: a real iPhone, a real Android phone with this APK, two linked PCs, real AI engines with the new start text, the Linux AppImage swap. Exact hashes are in release.json and SHA256SUMS.txt.

Autark 0.3.2

Autark 0.3.2 for Windows x64, Linux x64 AppImage and macOS universal (Apple silicon and Intel).

New since 0.3.1:

• One company on every PC: a PC that links as you takes the company's name, your name and your settings. Settings now travel section by section, so a change on one PC no longer resets another part (0.3.1 could empty the company name when a new PC linked). Linked PCs need the same version to share settings and plan logins.
• Sign in once: AI plan logins (Codex, Claude Code, Gemini CLI) travel between your own PCs inside the encrypted link, the newest one wins; never to an employee's PC, never to an agent. Claude Code on a Mac keeps its login in the Keychain and still signs in there. Stored files and pictures, knowledge and found plan accounts travel too.
• Status is part of the chat: "working", the steps and "Worked 41 s · 6 steps" live in the chat's own line, so every linked PC and the phone see the same thing.
• Calls: a call shows as one bubble in the chat; a click opens the whole transcript, both sides. The quick spoken answer also serves chats with several agents, and the call keeps waiting while an agent still works.
• Secrets: select all, none or single entries, export them as a CSV file (names and descriptions come back on import, also in another company) and delete them; a login shows its e-mail. Entries the app itself uses start unselected.
• Agents and companies: agents see the companies on this PC and can act in another of yours; they look first and then act.
• Codex: opening a Codex thread gets 120 s and a slow start no longer blocks the account for 5 minutes; Autark's Codex threads no longer appear in the Codex app's chat list.
• Phone: the pairing QR carries a Tailscale https address when there is one and never a PC-only address; a 6-digit code pairs an iPhone's installed app.
• Agents speak as themselves: every prompt, skill, mode and tool text is written in the agent's own first-person voice. After the update, an agent whose standard instructions you edited gets one review of the changed lines.
• Fixes: an agent's own skills are in backups again; a model switch line says why again.

Verification: typecheck, import boundaries and the build passed; the full unit run passed (4,937 tests, 4,934 passed, 3 skipped, none failed), the e2e runs passed (24 of 24) and so did the window checks for start-up, first run, the update entry and the settings pages (4 of 4); before the snapshot the whole e2e suite (96 tests, 93 passed, 3 skipped) and the window tests of the changed areas passed too. Native packaged startup, SQLite, the speech addon, a demo chat and the first desktop window (sandboxed, context isolation on) passed on Windows, Linux, Apple silicon and Intel, with 220 compiled application files checked in every package. Sandbox and context isolation remain enabled.

Windows and Linux update in the app. The Mac app can replace itself with a later version where macOS allows it; that path has not yet run on a real Mac. The Mac package is ad-hoc signed, without Apple Developer ID or notarization; Windows remains unsigned. The update from 0.3.1 was not run on a PC before release. Not established: two real PCs sharing logins and live status, a real phone, a fresh Windows installation, the update on macOS and Linux, normal user-device AppImage/FUSE acceptance. Exact hashes are in release.json and SHA256SUMS.txt. Product sources remain private. This release again carries the three downloads under their old names (workforce-*), byte for byte the same files, so older links keep working.

Autark 0.3.1

Autark 0.3.1 for Windows x64, Linux x64 AppImage and macOS universal (Apple silicon and Intel).

New since 0.3.0:

• An area per chat: a collapsible area right above the chat holds that chat's browser tabs, notes, media, video and files; the pane at the right keeps your own tabs. Each agent has its own area on its page. Browser tabs behave more like Chrome: "+" right after the last tab, preview tabs for pages an agent opens, the strip in the window's top row where there is room for it.
• Linking PCs: Autark's own meeting server is the default, so two PCs in different networks find each other by Remote ID ("Connect to my other PC" on the first start and in Settings › Devices; an agent can do it too). Linked PCs of one company share chats, tasks, agents, settings, memory and secrets (inside the encrypted link); each agent runs on its home PC; an employee's PC gets only that person's part. AI plan sign-ins are not copied between PCs.
• Several companies on one PC: the profile menu lists them, switches between them and creates a new one; each has its own data folder and settings.
• Secrets: name and value side by side on the page, a pasted .env splits into rows, drop a browser's password export, a .env or JSON file; agents import a file by its path without seeing a value.
• Models: every setting shows the model that runs instead of "Auto"; no fallback switches. The first start explains which models answer now, what a real decision and search model would change, and how to get one.
• Working together: agents find their own way on the PC first (a signed-in browser, an export, a colleague with other tools), take you along on a new kind of step others will see, and report steps they took on their own as important. Notifications play a sound by default; to-dos, blockers and important messages stay until opened. A timeout of the app no longer reads as "you declined". The Plus menu never greys out its entries.
• Fixes from live tests: a manager sees and edits the schedules of its team; the answer to your own message is never silent; an update of the standard system prompt shows each agent only what changed, filled in for it.

Verification: typecheck, import boundaries and the build passed; the full unit run passed (4,823 tests, 4,820 passed, 3 skipped, none failed), the e2e runs passed (24 of 24) and so did the window checks for start-up, first run, the update entry and the settings pages (4 of 4). Native packaged startup, SQLite, the speech addon, a demo chat and the first desktop window (sandboxed, context isolation on) passed on Windows, Linux, Apple silicon and Intel, with 220 compiled application files checked in every package. The meeting server ran live: two Autark runtimes on one PC, without LAN discovery, found each other by Remote ID through it and linked. Sandbox and context isolation remain enabled.

Windows and Linux update in the app. The Mac app can replace itself with a later version where macOS allows it; that path has not yet run on a real Mac. The Mac package is ad-hoc signed, without Apple Developer ID or notarization; Windows remains unsigned. The update from 0.3.0 was not run on a PC before release. Not established: a fresh Windows installation, the update on macOS and Linux, linking two PCs in two real networks, normal user-device AppImage/FUSE acceptance. Exact hashes are in release.json and SHA256SUMS.txt. Product sources remain private. This release again carries the three downloads under their old names (workforce-*), byte for byte the same files, so older links keep working.

Autark 0.3.0

Proactive Agent Workforce is now Autark. Windows x64, Linux x64 AppImage and macOS universal (Apple silicon and Intel) are now 0.3.0.

The app, its installer and its files carry the new name: autark-windows-x64.exe, autark-mac-universal.dmg, autark-linux-x64.AppImage. On its first start, 0.3.0 moves the data folder once, in place, from the old name to Autark, so there is one app and one folder. The workspace folder ~/Workforce keeps its name. This release also carries the three downloads under their old names (workforce-windows-x64.exe, workforce-mac-universal.dmg, workforce-linux-x64.AppImage), byte for byte the same files, so existing links keep working. The update manifests name only the new files.

New since 0.2.9: a short first start (name and company, then the manager asks the first question in the chat), settings on several pages, AI providers as a section of settings.json, side tabs like a browser (global, per chat and per agent), rewritten skills, Gemini Live as a second real-time voice provider, and each agent's last prompt as a file. Product sources remain private.

Verification: typecheck, import boundaries and the build passed. The full unit run passed: 4,677 tests, 4,674 passed, 3 skipped, none failed. The e2e runs passed (24 of 24), and so did the window checks for start-up, first run, the update entry and the settings pages (4 of 4). Native packaged startup, SQLite, speech addon, a demo runtime chat and the first desktop window passed on Windows, Linux, Apple silicon and Intel; 219 compiled application files were checked in every package. On one Windows 11 PC with Smart App Control on, the installed 0.2.9 updated itself to this exact build through a local copy of the update feed: it downloaded only the changed parts (about 15 MB), installed silently and started Autark, which moved the data folder to %APPDATA%\Autark with agents, chats and settings intact; one app entry and one shortcut were left and the old update cache was removed. The old, emptied program folder stayed behind and was removed by hand. Sandbox and context isolation remain enabled.

Windows and Linux update in the app. Mac: 0.2.9 gets 0.3.0 as a manual download once (its download link still works). From 0.3.0 on, the Mac app can replace itself with a later version where macOS allows it; that path has not yet run on a real Mac. The Mac package is ad-hoc signed, without Apple Developer ID or notarization. Windows remains unsigned. Operating-system trust policies still apply.

Verification does not establish a fresh Windows installation, the update on macOS and Linux, normal user-device AppImage/FUSE acceptance, the broad UI suite or live provider/device features. Exact hashes and evidence are in release.json and SHA256SUMS.txt.

Workforce 0.2.9

Windows x64, Linux x64 AppImage and macOS universal (Apple silicon and Intel) are now 0.2.9.

This is a fresh snapshot of the 1 November development state, including the simplified settings and model system, scheduling in the composer and the file-based memory tree. Product sources remain private.

Verification: all four TypeScript layers, import boundaries and six build targets passed. Native packaged startup, SQLite, speech addon, a demo runtime chat and the first desktop window passed on Windows, Linux, Apple silicon and Intel. The same 218 compiled application files were checked in every package; the universal Mac ZIP also passed deep signature validation on Intel. Sandbox and context isolation remain enabled.

The full unit run recorded 4,268 passes, one Linux timing assertion failing under Windows, and two skips. That timing test passed under native Linux without a product change. Runtime/upgrade checks initially recorded 23 passes and one outdated memory-ID assertion. The corrected upgrade test verifies the preserved text, scope, kind, old-ID alias and another restart; both upgrade checks pass. Crash recovery, task/chat flows and the other original checks passed. These results are recorded separately in release.json.

All three platform update manifests and permanent download names are preserved. Windows and Linux use their existing in-app update channels. Mac updates remain a manual download: its package is ad-hoc signed, without Apple Developer ID or notarization. Windows remains unsigned. Operating-system trust policies still apply.

Verification does not establish a fresh Windows installation, a complete native automatic-update/restart cycle, normal user-device AppImage/FUSE acceptance, the broad UI suite or live provider/device features. Exact hashes and evidence are in release.json and SHA256SUMS.txt.

Autark 0.2.8 — Windows, Linux and macOS

Windows x64, Linux x64 AppImage and universal macOS downloads are now version 0.2.8.

This is a snapshot of the ongoing agent/runtime/interface rebuild, captured on 30 October in an isolated release copy. The active development checkout and real user profiles were not changed. Product sources remain private.

Verification: native packaged startup, SQLite, speech addon, 226 byte-matched compiled application files, fake-engine runtime chat and the first desktop window passed on Windows, Linux, Apple silicon and Intel. Renderer sandboxing and context isolation remain enabled. The identical universal Mac ZIP also passed deep signature validation on Intel. Four production type layers, the application build, import boundaries, 14 runtime/upgrade E2E checks and 9 NSIS compiler/integrity checks passed. The dependency audit reports no known vulnerabilities.

Verification limits: the broad 7,275-test inventory still has 15 open assertions after environment-specific reruns (7,249 pass, 11 skipped). The full test-source type graph was not completed. A fresh Windows installation and a complete native automatic-update cycle were not rerun for 0.2.8. Real provider accounts, devices and all platform features are not fully accepted. Details and exact file hashes are in release.json and SHA256SUMS.txt.

System trust: Windows remains unsigned, so SmartScreen may warn and Smart App Control may block the installer. macOS is ad-hoc signed, without Developer ID or notarization, and may be blocked by Gatekeeper. Linux requires FUSE 2, a working Chromium sandbox and a running secure system keyring. Its native desktop checks used a configured Ubuntu VM; normal user-device AppImage/FUSE acceptance remains open. No security policy was disabled and no plaintext secret-storage fallback was introduced.

The permanent download filenames and platform manifests are preserved. Future single-platform releases must carry the last packages and matching manifests of the other platforms so all direct links continue to work.

Workforce 0.2.7 - Windows update restart fix

Windows 0.2.7 repairs Restart to Update: the installer opens the installed executable directly, including when a kept Start-menu link is stale. Installer-start errors restore the paused app, retain the download and permit an explicit retry. Safe update states/error codes are recorded in the main log.

Local Windows packaging also works without starting its temporary NSIS generator. The upstream static reader reconstructs the uninstaller and verifies the original NSIS CRC. No OS security/trust policy or installed dependency is modified. Windows remains unsigned.

Verification: 40 focused updater/lifecycle tests, 9 real NSIS compiler/integrity tests, main and reader types, boundaries, six build targets, the exact packaged application, a synthetic 0.2.6 profile upgrade and the complete native automatic-relaunch probe passed. The native probe uses fixture versions 0.0.2/0.0.3 with the final main bundle, its own product ID/profile/workspace, a missing shortcut target, a preserved task and desktop shortcut, and the new main state current.

Based on shipped 0.2.6 plus the scoped update and packaging repair. Existing broad project-test and real-account/device acceptance gaps remain open; see release.json. The reported other computer was not accessed, so its exact prior cause is not established. No real user profile was installed/reset. Linux/macOS remain 0.1.7; application sources remain private.

Existing Windows apps use the normal update feed. If an older client keeps offering the same restart, download the Windows installer below and run an ordinary installation once. Normal updates/reinstallations retain app data.

Workforce 0.2.6 - Desktop update (26 October 2026)

Windows 0.2.6 is the existing local desktop development snapshot from 26 October 2026, released without product or test changes. Existing Windows installations discover it through the normal in-app update feed.

Since 0.2.5, the existing snapshot includes the revised fixed application frame and headers, simplified settings and account setup, the open settings/prompt/agent folders, and changes to Remote, browser work, schedules and agent continuation. TeleCoding and OpenCode were removed in that snapshot. This release does not claim completion of every feature or real-account acceptance.

Completed release verification:

• Fresh dependency install; all six build targets, import boundaries (57 existing warnings), application-source typechecks across four layers and Windows-x64 NSIS package build passed.
• Focused runtime E2E: 25/25 passed, covering chat/task/to-do flows, My day, old-profile upgrade and crash recovery.
• Real Electron windows: 3/3 passed (startup/demo chat, first-run flow, update entry).
• A synthetic profile created by 0.2.5 upgraded to 0.2.6 and restarted again: profile/theme, completed setup, agent, chat, messages and My-day task retained; settings.json written. This does not install into the person's profile.
• Exact packaged executable: version 0.2.6, Electron 44.9.3, fresh isolated demo profile, chat and My-day creation, no renderer exceptions; light/dark, 640x480 and a 390-pixel viewport checked. 286 built app/resource files matched app.asar byte-for-byte; private development folders excluded.
• The first package probe timed out after 30 seconds while capturing a My-day screenshot, after its functional checks. The unchanged executable was checked again in another fresh isolated profile; the repeat passed.
• npm audit: zero reported vulnerabilities; dependencies unchanged. The previously failing CLI-detection timing file passed unchanged in isolation: 5/5.

Known verification limits and open issues:

• Development snapshot. The complete project typecheck still reports two errors in test sources (notice assertions and a missing declaration for the layout-test helper); application-source checks passed with a separate runtime release config excluding tests and explicitly including DOM stream types.
• The broad unit run was stopped after stalling in Git merge/worktree checks. It is incomplete and had three observed failures: CLI detection timing, the device-tool inventory expectation, and missing CSS-overlay protection class aliases on new Remote/Secret forms. The full suite is not certified green. The CLI detection file was subsequently rerun unchanged in isolation (see verification). The other two checks remain open.
• All code and test edits attempted during release investigation were reverted. The shipped product is the existing local snapshot; only package version and release metadata changed.
• Focused E2E and Electron checks use isolated demo profiles. Real model inference, external calendar accounts, physical devices, microphone/overnight use and the previously documented intermittent recorder issue were not accepted in this release.
• No installation or update/restart in the active user profile. Windows installer unsigned. Linux and macOS packages and manifests remain at 0.1.7. Feedback has no configured operator sender.

Private source code and project documentation remain private. SHA256SUMS.txt and release.json record hashes and evidence; latest.yml records the installer SHA-512.

Workforce 0.2.5 - My day and calendars (24 October 2026)

Windows 0.2.5 contains the current desktop development snapshot from 24 October 2026. Existing Windows installations discover it through the normal in-app update feed.

Included since 0.2.4:

• My day with personal to-dos, handed-off work, daily/weekly calendar, planning, morning briefing, estimates and focus timers; calendar connection settings.
• Work splits an input into separate items and routes them to My day or the team. Home uses five fixed sections; Team includes activity and people pages.
• Chat avatars, expandable work messages with task links and grouped call history. Repeated Open on Phone entries were removed; phone setup is in Settings > Remote.
• The quota refresh correction added during the release build: refresh at startup, provider events and bounded serial reads (Codex every 15 seconds, Claude Code every 60 seconds, with failure backoff).
• Electron updated from 44.7.2 to 44.9.3; patched fast-uri and undici lockfile dependencies. The final npm audit reports zero vulnerabilities. Electron advisory: GHSA-jr5w-w6x2-84p9

Release verification:

• Fresh dependency installation; all seven build targets including TeleCoding, all four TypeScript layers and import boundaries passed (59 existing warnings).
• Complete unit suite on the initial frozen snapshot: 4967 tests, 4965 passed, 0 failed, 2 skipped. After the newer quota refresh correction was incorporated, the full affected accounts and engines unit areas were rerun: 233/233 passed. The complete unit suite was not repeated after that isolated correction; typechecks, build, E2E, windows and package verification all use the final snapshot.
• Focused runtime/browser E2E: initially 46/47 passed; one PWA screenshot capture timed out after 30 seconds. The full affected file was rerun without code changes: 2/2 passed, no unresolved failure. Focused real Electron window checks initially 8/10; two test-only corrections (calendar input focus and the existing live working-message UI), followed by 2/2 in a full rerun of both affected files. No unresolved window failure; application code unchanged by these test corrections.
• Exact packaged executable: version 0.2.5, Electron 44.9.3, fresh isolated demo profile, successful demo chat and My day to-do creation, no renderer exceptions. Light/dark, 640x480 and actual 390-pixel viewport screenshots reviewed.
• 299 built app/resource/vendor files verified byte-for-byte in app.asar; private development files excluded.

Limits:

• Development snapshot with open concept requirements; focused E2E/window checks, not every test in those collections.
• Real Google Calendar, real model inference, physical phone/two-PC, colleagues and overnight use were not tested in this release.
• The previously documented intermittent recorder Stop-button issue remains unresolved; that window test was not run for this release.
• No installation or update/restart in the active user profile; Windows installer unsigned.
• Linux and macOS packages and manifests remain at 0.1.7.
• Feedback remains local without an operator sender.

This release does not install into, reset or restart the active user profile. Real Google/phone/overnight capabilities remain subject to the documented acceptance work. Private sources and project documents remain private. SHA256SUMS.txt and release.json record hashes and evidence; latest.yml records the installer SHA-512.

Workforce 0.2.4 - Windows update (24 October 2026)

Windows 0.2.4 contains the current Agent OS development snapshot from 24 October 2026. Existing Windows installations can discover it through the normal in-app update feed.

Included in the current snapshot: the unified header and Windows caption layout, Remote connections, task center, model hints and routing guidance, onboarding paths, shared knowledge and skills, calls and people, media marks, recovery and safe start, plus the other integrated changes in the current source snapshot.

Verification performed for this release:

• Fresh dependency installation; all seven build targets, including the embedded TeleCoding view; all four TypeScript layers; import boundaries passed (61 existing warnings).
• Full initial unit run: 4610 tests, 4600 passed, 9 failed, 1 skipped. The nine failures were LF-only text expectations on Windows CRLF files. Only the nine test files were corrected; their complete rerun passed 58/58. No unresolved test failure remains; the full unit suite was not repeated after these test-only corrections.
• Focused runtime E2E: 41/41 passed, including profile upgrade, crash recovery, backup/restore, routing, quick tasks, Remote pairing between two local runtime processes, TeleCoding view and the terminal client.
• Focused Electron window checks: 5/5 passed (Remote, repair, safe start, columns/browser tabs, update controls).
• Exact packaged Windows executable started in a fresh isolated demo profile: version 0.2.4, runtime connection, demo chat and no renderer exceptions. Light/dark, 640x480 and an actual 390-pixel viewport checked; screenshots reviewed. All 299 built app/resource/vendor files verified byte-for-byte inside app.asar; private development files excluded.

Limits: development snapshot with open concept requirements. The complete E2E/window collections, real model inference, physical phone/two-PC and long-term acceptance were not run. This process does not install into, reset or restart the active user profile. Feedback remains local without an operator sender. The Windows installer remains unsigned; Linux/macOS packages and their manifests remain unchanged at 0.1.7.

Installer SHA-512 is recorded in latest.yml. SHA256SUMS.txt and release.json provide artifact hashes and detailed release evidence. Private sources and project documents remain private.