AYLITH
←

Tickets

Studio notes · Tickets

Changelog

Dated studio notes are distinct from package releases and current setup requirements.

  1. · added

    Tickets: file it, hand it to your agent

    Tickets 0.1.3 is the first published release: a local-first issue tracker for turning “I should fix that” into a saved task. File a ticket in its local browser UI or terminal TUI, then copy a composed prompt. With a supported local terminal and coding agent configured, a ticket can also open that agent on the task in the selected repo.

    The central UI lists tickets across every registered project, with status chips and a per-ticket action menu.
    Archived central-UI capture. Filter the board to one project with /project; this image does not establish which release binary produced it.

    What shipped

    • Three surfaces, one daemon. A browser UI (all projects at once, or one), a terminal TUI across every project, and framework-agnostic web components you can embed in a web app — all over a single local, auth-less REST + SSE API.
    • Configurable terminal handoff. With your terminal, shell, and coding agent set up, a ticket action starts that agent on the composed task in the selected repo. The daemon is local and has no user authentication.
    • Optional enrichment and Git history. AI enrichment needs a configured provider or CLI. The default Git store commits edits on an orphan branch and supports revision-backed undo. Plain folder storage does not have Git history or that undo path.
    • Configurable evidence. Before/after images and video can attach to a ticket when a media repository and publisher are configured. Installation alone does not grant hosted media publishing.

    Install

    For the 0.1.3 browser UI, download the matching standalone binary from the pinned v0.1.3 release. Linux and macOS have architecture-specific assets; Windows x64 has a separate .exe asset. The main/install.sh convenience installer follows the latest release and is not pinned to 0.1.3. The published 0.1.3 npm archives include libraries and CLIs but omit the browser app assets, so npm is not an equivalent browser installation for this release. The default Git-backed tickets init path requires Git 2.42 or later; tickets init --adapter folder avoids that requirement but has no Git revision history. After setup, run tickets serve for the local browser UI or tickets tui for the terminal view.