mi-lsp
Local CLI that indexes repos to find code, read exact ranges, and follow canonical docs.
Tested on macOS and Linux
Use it
macOS arm64
download install.sh to read before running
curl -fsSL https://raw.githubusercontent.com/fgpaz/mi-lsp/main/scripts/install/install.sh -o /tmp/install.sh && echo DONE && wc -c /tmp/install.shdownload sibling validator required by install.sh
curl -fsSL https://raw.githubusercontent.com/fgpaz/mi-lsp/main/scripts/install/validate-worker-manifest.js -o /tmp/validate-worker-manifest.js && echo DONE && wc -c /tmp/validate-worker-manifest.js && ls /tmp/*.sh /tmp/*.jsrun CLI-only install.sh for darwin-arm64
sh /tmp/install.sh
Where the README and reality differ
- README: curl -fsSL .../install-agent.sh | sh installs directly
What worked: download validate-worker-manifest.js next to install.sh before running install-agent.sh/install.sh (curl .../validate-worker-manifest.js -o /tmp/validate-worker-manifest.js)
Check that it works
mi-lsp --helpThe output should contain “version for mi-lsp”.
First thing to try
mkdir -p src/billing tests/billing .docs/wiki/05_requirements && cat > src/billing/retry.py <<'EOF'
"""Billing retry logic sample."""
RETRY_LIMIT = 3
def billing_retry(order_id, attempts=RETRY_LIMIT):
"""Retry billing for order."""
for i in range(attempts):
if charge(order_id):
return True
return False
def charge(order_id):
"""Charge order."""
return True
EOF
cat > tests/billing/retry_test.py <<'EOF'
from src.billing.retry import billing_retry
def test_billing_retry():
assert billing_retry("order-123") is True
EOF
cat > .docs/wiki/05_requirements/RF-GPH-010.md <<'EOF'
# RF-GPH-010 - Billing retry spec
Billing retry governs how the daemon restarts failed charges.
See billing_retry symbol.
EOF
echo SETUP_DONE && ls -R src tests .docsmi-lsp init . --name myapp --format toonIn your repository folder, run mi-lsp init . --name <workspace> --format toon to index it as a workspace.
Linux x86_64
download install.sh to read before running
curl -fsSL https://raw.githubusercontent.com/fgpaz/mi-lsp/main/scripts/install/install.sh -o /tmp/install.shdownload sibling validator required beside install.sh
curl -fsSL https://raw.githubusercontent.com/fgpaz/mi-lsp/main/scripts/install/validate-worker-manifest.js -o /tmp/validate-worker-manifest.jsinstall CLI with --skip-worker-install
sh /tmp/install.sh --skip-worker-install
Where the README and reality differ
- README: curl -fsSL .../install-agent.sh | sh (which fetches install.sh alone)
What worked: download https://raw.githubusercontent.com/fgpaz/mi-lsp/main/scripts/install/validate-worker-manifest.js beside install.sh before running it; install.sh calls node <script_dir>/validate-worker-manifest.js - README: mi-lsp nav search "billing retry" --include-content --workspace myapp
What worked: on a container workspace add --repo src: mi-lsp nav search ... --workspace myapp --repo src --include-content
Check that it works
mi-lsp init . --name myapp --format toon 2>&1The output should contain “ok: true”.
First thing to try
mkdir -p src .docs/wiki/05_requirements && cat > src/app.py <<'PY'
def hello_world(name):
"""Greet by name."""
return f"hello {name}"
def billing_retry(attempt):
"""Retry billing."""
return attempt + 1
PY
cat src/app.py && mkdir -p myapp 2>/dev/null; echo setup-donemi-lsp init . --name myapp --format toon 2>&1In your repository folder, run mi-lsp init . --name <workspace> --format toon to index it as a workspace.
What it does
- Find a symbol by nameTested
How to use it
- Index your repo with
mi-lsp init . --name <workspace> --format toon. - Run
mi-lsp nav find <symbol> --workspace <workspace> --format toonto get the file, line and definition.
- Index your repo with
- Search text and see matching code inlineTested
How to use it
- Index your repo with
mi-lsp init . --name <workspace> --format toon. - Run
mi-lsp nav search "<your text>" --workspace <workspace> --repo <repo> --include-content --format toonto see matches with their code lines.
- Index your repo with
- Read exact line ranges from one or more filesTested
How to use it
- Index your repo with
mi-lsp init . --name <workspace> --format toon. - Run
mi-lsp nav multi-read <file>:<start>-<end> <file>:<start>-<end> --workspace <workspace> --format toonto print those lines.
- Index your repo with
- Browse the project wiki and governance docsNot tested
How far pickfit got
macOS arm64
- Installs
- Starts
- 3 of 4 features work
- Works offline
Linux x86_64
- Installs
- Starts
- 3 of 4 features work
- Works offline
Other systems
Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- Find a symbol by name
- Search text and see matching code inline
- Read one or more exact file ranges
- See what a change affects (callers, tests, docs)
- Navigate the wiki / governance docs
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
macOS arm64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 0.16.7
Differences the test machine hit
- README: install-agent.sh adds CLI plus mi-lsp skill
In the test: CLI installs fine but the trailing `npx skills add fgpaz/claude-skills` step fails with authentication failure for that repo; CLI-only install.sh avoids it - README: mi-lsp nav search "billing retry" --include-content --workspace myapp
In the test: on a container workspace add --repo <repo> to get inline content instead of a scope preview
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version v0.16.7
Differences the test machine hit
- README: curl -fsSL .../install-agent.sh | sh installs CLI
In the test: sh /tmp/install.sh --skip-worker-install; plain install fails at worker install stage with 'staged worker did not pass protocol verification' - README: installer verifies SHA256 checksum
In the test: release tarball (~270MB) downloaded and verified by installer at install time; binary content cannot be read beforehand