tickloop 0.2.5

Installer and launcher for the official Tickloop terminal agent
Documentation
  • Coverage
  • 50%
    1 out of 2 items documented0 out of 1 items with examples
  • Size
  • Source code size: 21.8 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 70.4 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 1s Average build duration of successful builds.
  • all releases: 1s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • crates.io
  • Dependencies
    • —
  • Versions
  • Owners
  • griffinqiu

Tickloop

Install the official Tickloop terminal agent on macOS:

cargo install --locked tickloop
tickloop

This crate contains the installer and launcher only. It does not include the Tickloop application's source code. Cargo compiles the small launcher locally; on first use it downloads the matching official macOS release from tickloopai/homebrew-tap on GitHub, verifies SHA-256 and the archive contents, and installs the complete tickloop, tickhost, and tick-reader bundle.

Apple Silicon and Intel Macs are supported. Installation needs Rust 1.89 or newer, network access and the macOS system curl, shasum, and tar commands. Downloads happen when launching the program, never while compiling the crate.

The Cargo installation includes tickloop, tl, tickhost, and tick-reader. The verified application lives in .tickloop inside the Cargo installation root (~/.cargo/.tickloop by default). Existing Homebrew and native installations are not replaced; ensure your intended installation is first on PATH.

The application's normal background updater and tickloop update keep this private runtime current without replacing Cargo's launcher or stopping running Agents and Ticks. The crate version specifies the minimum initial application version, not a pin that disables application updates. cargo install tickloop also updates the launcher when a newer crate version is available.

First launch can take longer while downloading. Failed or invalid downloads do not replace an existing runtime. Cached application versions are retained for running processes. The launcher passes command arguments and the working directory unchanged to the official program.