pickfit

BrowseDeveloper CLIs

motita

Autonomous AI agent in Go that runs tasks verified by user checks.

Tested on Linux

Use it

Linux x86_64

You need first

  • System packages: OpenSSL 3
  • Keys or accounts: API key
  1. Download installer script only

    curl -fsSL https://motita.kodingvibes.com/install.sh -o /tmp/install.sh && wc -c /tmp/install.sh && head -c 2000 /tmp/install.sh
  2. Run installer script after reading

    openssl version; echo "---"; sh /tmp/install.sh

Check that it works

motita --version

The output should contain “motita v4.82.0 (linux/amd64)”.

First thing to try

motita gateway stop

What it does

  • Confirm tasks are done with fixed checks
    Not tested
  • Run background agents in parallel on git branches
    Not tested
  • Use any model through a subscription or API
    Not tested
  • Control the agent from a TUI, web UI or API
    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

  • Split a big job across background agents on git branches

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 v4.82.0

Differences the test machine hit

  • README: Then just run motita. A 5-step setup picks your provider, model and the check
    In the test: motita config is an interactive 5-step wizard asking for Provider [1] and timed out after 30s with stdin closed; gateway stop works non-interactively
  • README: motita gateway start
    In the test: motita gateway start did not come up within 10s; log at ~/.motita/workspace/motita.log says the LLM key is missing, so a configured provider/API key is required before the gateway/Web UI runs

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.