• v1.0.0-beta.98 91f5e1c47f

    Beta 0.98 Pre-release

    ai17z-mirror released this 2026-11-20 13:58:29 +00:00 | 0 commits to main since this release

    Install

    Copy the command for your operating system and paste it into a terminal.

    Windows 10 and 11: open Windows Terminal and paste:

    irm https://raw.githubusercontent.com/ShiftAboveCtrl/ai17z/main/install.ps1 | iex
    

    macOS 13 or newer (Apple silicon and Intel): open Terminal and paste:

    curl -fsSLO https://raw.githubusercontent.com/ShiftAboveCtrl/ai17z/main/install-ai17z-macos.sh && bash install-ai17z-macos.sh
    

    Ubuntu 22.04 or newer (amd64 and arm64): open a terminal and paste:

    curl -fsSLO https://raw.githubusercontent.com/ShiftAboveCtrl/ai17z/main/install-ai17z-ubuntu.sh && bash install-ai17z-ubuntu.sh
    

    If GitHub is down, the same installers are on AI17Z Code, AI17Z's own server:

    irm https://code.ai17z.io/AI17Z/ai17z/raw/branch/main/install.ps1 | iex
    
    curl -fsSLO https://code.ai17z.io/AI17Z/ai17z/raw/branch/main/install-ai17z-ubuntu.sh && bash install-ai17z-ubuntu.sh
    

    The installer checks your system, offers to install anything missing, then
    installs AI17Z and starts it. It downloads from GitHub, or from AI17Z Code when
    GitHub cannot provide a file, and checks every download against this
    release's SHA256SUMS.txt before it is used. AI17Z needs Docker, and
    Google Chrome for browser features. On Windows the installer also sets up
    WSL 2 and Node.js 22 or newer through Microsoft's own tools, and opens
    AI17Z when it is ready. No security setting is changed.

    Full installation guide ·
    What the installer does ·
    Uninstalling

    What's new

    Beta 0.98 lets an owner publish a long development update as a short X thread, and removes two database deadlocks between agent locks and foreign key checks.

    What changed since Beta 0.97

    Development updates can be threads. An update sent as parts (one to six pieces, each at most 280 Unicode code points) is reviewed and published as a thread instead of one post. A one-part update is the same single post as before.

    • The Review screen lists every part in order with its position and character count. The owner makes one decision for the whole thread, and can edit each part before it goes out, as long as the number of parts stays the same. Attachments go with the first part.
    • The command line accepts approve <updateId> --parts-file <json-file>, and npm run dev-updates -- split --text "..." prepares a paragraph and sentence split.
    • The account needs both post and reply permission. Part one is an ordinary post and each later part replies to the previous part once its status id is confirmed. Every part goes through the ordinary executor, so safety and policy checks cover the whole thread before anything is sent and run again at each send.
    • Account cadence and agent rate limits are checked for every part together, once. That admission is recorded on the update, so a recovery cannot admit the same thread a second time. The project ceiling counts a thread as one update, and the account's action limits still count every published part.
    • If a part fails, publishing stops and every part that did go out is recorded with its link. A recovery skips parts already done and asks the platform before retrying one whose outcome is unknown. An unknown outcome stops and never sends again. Rehearsal checks every part without creating a public reply target.

    Agent locks no longer deadlock foreign key checks. The Studio risk watches, the coin alerts sync and a trade mandate activation could each wait on a lock another path held while inserting a row that points at the same agent, and Postgres ended one of them with "deadlock detected". Those paths now take weaker row locks that still keep two workers on the same agent apart, and take their locks in one fixed order: agent, then Studio binding, then radar source. Playbook imports use the same weaker lock. A new regression test drives the real paths and failed before the fix.

    This adds migrations 0143 and 0144.

    Known limits

    Threads need an account that has granted reply permission as well as post permission. A development update with a single part behaves as it did in Beta 0.97. The thread publisher has been exercised against mocks and test databases, and no run used a live X account.

    Upgrading

    Use the updater belonging to the installation you want to update. Beta 0.98 uses the semver tag v1.0.0-beta.98. GitHub Actions builds the Windows, Ubuntu and macOS packages and verifies the published release files.


    What changed since v1.0.0-beta.97, commit by commit
    • Beta 0.98
    • Publish long development updates as threads (#50)
    • Stop agent locks deadlocking foreign key checks (#49)
    Which file is which

    You do not need to download anything by hand: the commands above fetch what
    they need. These are here for anybody who wants a specific file.

    File What it is
    AI17Z-Setup-1.0.0-beta.98.exe Classic Windows installer. Unsigned; the command above is the recommended route
    install-ai17z-macos.sh macOS installer script, the same file the macOS command runs
    install-ai17z-ubuntu.sh Ubuntu installer script, the same file the Ubuntu command runs
    AI17Z-macos-arm64-1.0.0-beta.98.tar.gz, AI17Z-macos-x64-1.0.0-beta.98.tar.gz macOS application, Apple silicon and Intel
    ai17z_1.0.0-beta.98_amd64.deb, ai17z_1.0.0-beta.98_arm64.deb Ubuntu packages
    SHA256SUMS.txt SHA-256 of every file
    SHA256SUMS.txt.sigstore.json Signature of SHA256SUMS.txt, verifiable against ci/cosign.pub
    install.ps1 Used by the installer: the file behind the Windows command
    Install-AI17Z-1.0.0-beta.98.ps1 Used by the installer: the Windows setup program it checks and runs
    AI17Z-App-1.0.0-beta.98.zip Used by the installer: the application the Windows setup program installs
    release-manifest.json Used by the installer: what this release is and what it needs, read before an update
    release-notes.md Used by the app: these notes, shown on its update screen

    The setup audit (AI17Z-Setup-Audit-1.0.0-beta.98.json) and a signature for every
    file are published on AI17Z Code.

    The macOS and arm64 Ubuntu packages are assembled on Linux and accepted only
    when every native file in them is byte for byte one a machine of that platform
    built and ran (ci/native-references.json).

    Verify a download
    cosign verify-blob SHA256SUMS.txt --bundle SHA256SUMS.txt.sigstore.json --key cosign.pub
    sha256sum --check --ignore-missing SHA256SUMS.txt
    
    e135b547a668e322e53ede43771afcc12992e3b8b73d6ddf1a707822e6f6d98d  AI17Z-Setup-1.0.0-beta.98.exe
    27942d3a537aac05857040b9acd2b993390709738a16c22c5a3af3fe24f4a4de  install.ps1
    c4b1bbbed2ffd79bb698c2f6dbeacaa1c64e863aa370d7f160e0b5e650d9599b  Install-AI17Z-1.0.0-beta.98.ps1
    053b5450940a29a0767bd576f47a45cb249cdf78c2514dc92b0d89ed8396c4c6  AI17Z-App-1.0.0-beta.98.zip
    ddfa99cc627884a7004a7d04317a9f1424d9716d4a91e7b6705f6d2c782eaed6  install-ai17z-macos.sh
    d5ec40e5d07aa53cbf51ca905b0e1003e2c04d53bafe3fdcbebcb4dd64c00b5d  install-ai17z-ubuntu.sh
    db86fa27a0d2e0072421d4689fd058203cf55936de2d465be53f3171fb5542e2  ai17z_1.0.0-beta.98_amd64.deb
    a8debe97c09011a586fbc0f7bd4dc06441a488ed1a8297f8acebda59d4503263  ai17z_1.0.0-beta.98_arm64.deb
    9c843e3eb9f80fc1b2108b5cf3d06ea41911e7dde57f338b009bdaafa5c105b0  AI17Z-macos-arm64-1.0.0-beta.98.tar.gz
    9c905186cdb0b6285ce2558cfd06ebc7c781c9f2746200af1096dd92ef8c2c9f  AI17Z-macos-x64-1.0.0-beta.98.tar.gz
    

    Install AI17Z only with the commands above or from this release page.
    Nowhere else distributes it.

    Downloads