pickfit

BrowseDeveloper CLIs

Open Walnut

Self-hosted web page to run Claude Code sessions on laptop and remote boxes with tasks and notes.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node 22 or newer for npm package
  • System packages: git for checkout route, Bun 1.4.4 or newer for checkout route, Claude Code signed in
  1. install via npm candidate 1

    npm install -g open-walnut
Where the README and reality differ
  • README: CLI lists `walnut projects` and `walnut sessions` with no prerequisite stated
    What worked: start the web server first with `walnut web` (background on port 3456), then the commands return empty lists

Check that it works

walnut --help

The output should contain “Start the web server”.

First thing to try

walnut web --port 3456
walnut projects

What it does

  • Run Claude Code sessions from one web page
    Not shown working
  • Run sessions on your laptop and on remote hosts
    Not tested
  • Keep sessions running when you disconnect
    Not tested
  • Review the diff for each session
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • Run and monitor multiple Claude Code sessions side by side
  • Inspect per-session diff and send review back to session
  • Manage tasks and search notes
  • Use same web app for laptop and remote SSH host sessions
  • Start coding sessions and run scheduled routines

An alternative to Notion.

How pickfit tested it

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

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.6.20

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.