pickfit

BrowseDeveloper CLIs

FutureOS

One Rust agent core driving TUI, desktop, mobile, CLI and chat apps.

Use it

Before you install: known vulnerabilities

pickfit found 4 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:pulldown-cmark 0.13.4 Exponential event growth with `ENABLE_WIKILINKS` (RUSTSEC-2026-0414, high, fixed in 0.13.5)
  • crates:quick-xml 0.26.0 Quadratic run time when checking a start tag for duplicate attribute names (RUSTSEC-2026-0194, high, fixed in 0.41.0)
See 2 more

Linux x86_64

You need first

  • Needs the network
  • Keys or accounts: model provider API key
  1. Download v2.0.1 CLI tarball with checksum

    curl -fsSL https://dl.future-os.cn/releases/2.0.1/FutureOS_2.0.1_linux_x86_64-cli.tar.gz -o /tmp/future-cli.tar.gz
  2. Extract future to ~/.local/bin and run future init

    tar -xzf /tmp/future-cli.tar.gz -C "$HOME"/.local/bin && chmod +x "$HOME"/.local/bin/future && future init
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

curl -fsSL https://dl.future-os.cn/releases/2.0.1/FutureOS_2.0.1_linux_x86_64-cli.tar.gz -o /tmp/future-cli.tar.gz
tar -xzf /tmp/future-cli.tar.gz -C /home/sbx/.local/bin && chmod +x /home/sbx/.local/bin/future && future init
future --version
future doctor

Check that it works

future --version

The output should contain “future v2.0.1”.

First thing to try

future doctor

Run future doctor to check that the tool is set up correctly.

What it does

  • Use one agent in the terminal, desktop and mobile
    Not tested
  • Run long goals with verification checkpoints
    Not tested
  • Schedule prompts to run as recurring tasks
    Not tested
  • Control tool use with approvals and sandboxing
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • parse PDF/Word files and search the web via agent
  • run scheduled recurring work on a timetable
  • fork and clone conversation sessions

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version v2.0.1

Differences the test machine hit

  • README: curl -fsSL https://dl.future-os.cn/install.sh | bash works on macOS/Linux
    In the test: Script takes Debian .deb path (dpkg detected) and runs `sudo apt-get install -y pkg`, but box has no sudo; installed the prebuilt linux-x86_64-cli tarball (same v2.0.1, SHA-256 verified) by extracting `future` to ~/.local/bin and running `future init`.
  • README: Installer provides desktop app + unified `future` CLI
    In the test: CLI-only tarball contains just the `future` binary, so `future doctor` reports future-tui, future-desktop and future-channel as not found on PATH.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.