pickfit

BrowseLocal AI tools

AOCI-CODE

Local-first MCP server and Go CLI that maintains a persistent Git-versioned index of codebase and database schema for coding agents.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

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

  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status (GHSA-5cgq-3rg8-m6cv, critical, fixed in 0.52.0)
See 9 more
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-89gr-r52h-f8rx (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-f5wc-c3c7-36mc (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-jppx-rxg9-jmrx (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-rm3j-f69w-wqmq (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-v778-237x-gjrc (critical), fixed in 0.31.0
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-vgwf-h737-ff37 (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-x527-x647-q7gg (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-8c26-wmh5-6g9v (high), fixed in 0.0.0-20220314234659-1baeb1ce4c0b
  • go:golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 — GHSA-gwc9-m7rh-j2ww (high), fixed in 0.0.0-20211202192323-5770296d904e

4 more findings not listed here.

Linux x86_64

You need first

  • Runtimes: go
  • System packages: make

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. download Go 1.23.6 tarball

    curl -fsSL https://go.dev/dl/go1.23.6.linux-amd64.tar.gz -o /tmp/go.tar.gz
  2. extract Go to ~/.local/go and link to ~/.local/bin

    mkdir -p $HOME/.local/go && tar -xzf /tmp/go.tar.gz -C $HOME/.local/go --strip-components=1 && mkdir -p $HOME/.local/bin && ln -sf $HOME/.local/go/bin/go $HOME/.local/bin/go
  3. git clone aoci-code

    git clone https://github.com/aoci-spec/aoci-code.git
  4. mkdir -p build && CGO_ENABLED=0 go build -o build/aoci ./cmd/aoci

    cd aoci-code && mkdir -p build && CGO_ENABLED=0 go build -o build/aoci ./cmd/aoci && ./build/aoci --version
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://go.dev/dl/go1.23.6.linux-amd64.tar.gz -o /tmp/go.tar.gz
mkdir -p $HOME/.local/go && tar -xzf /tmp/go.tar.gz -C $HOME/.local/go --strip-components=1 && mkdir -p $HOME/.local/bin && ln -sf $HOME/.local/go/bin/go $HOME/.local/bin/go
git clone https://github.com/aoci-spec/aoci-code.git
cd aoci-code && mkdir -p build && CGO_ENABLED=0 go build -o build/aoci ./cmd/aoci && ./build/aoci --version
cd aoci-code && mkdir -p build && CGO_ENABLED=0 go build -o build/aoci ./cmd/aoci && ./build/aoci --version
mkdir -p /tmp/testrepo && cd /tmp/testrepo && git init -q && git config user.email "a@a.com" && git config user.name "a" && echo "hello" > README.md && git add . && git commit -qm init && AOCI=/home/sbx/work/aoci-code/build/aoci

# F1: init + scan delivers codebase context
$AOCI --repo /tmp/testrepo

Check that it works

cd aoci-code && mkdir -p build && CGO_ENABLED=0 go build -o build/aoci ./cmd/aoci && ./build/aoci --version

The output should contain “aoci version dev”.

First thing to try

mkdir -p /tmp/testrepo && cd /tmp/testrepo && git init -q && git config user.email "a@a.com" && git config user.name "a" && echo "hello" > README.md && git add . && git commit -qm init && AOCI="$HOME"/work/aoci-code/build/aoci

# F1: init + scan delivers codebase context
$AOCI --repo /tmp/testrepo

What it does

  • Detects code changes and guides agents to update affected index entries
    Tested
  • Delivers whole codebase and database schema context to agents before they act
    Not shown working
  • Supports MySQL and PostgreSQL table-level indexing alongside code
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • provide long-term codebase context to coding agents without re-reading repository each task
  • index codebase and database schema into Git-versioned map
  • maintain index automatically after verified code changes

An alternative to CodeGraph, RAG and LSP.

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 2 Nov 2026
  • Version dev

Differences the test machine hit

  • README: prerequisites: go, make - make build
    In the test: make not present in box; built directly with CGO_ENABLED=0 go build -o build/aoci ./cmd/aoci
  • README: ./build/aoci --version shows 0.1.0-rc23
    In the test: source build without LDFLAGS reports dev (commit none, built unknown)

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.