Watchlist

Tools listed in index that aren't ready for actual use yet. Either too young (alpha, single-platform, single-author), too narrow (one-feature demo that may not grow), or too dependent on outside circumstances (a vendor's API, a regulatory window, a single corporate sponsor). The point of this page is to come back periodically and re-decide: graduated, abandoned, or still waiting.

How to use

Tag a toolbox entry with watchlist in its frontmatter and add a row here. Each row says what we're waiting on and when to re-check. When the verdict is in, remove the row and either drop the watchlist tag (graduated) or note the abandonment in the toolbox page itself (and keep the page — abandoned tools are still useful as references).

What "check later" means

Concrete signals to look at on each re-visit:

Activity — commits in the last 90 days, recent issues triaged, PRs merged
Star trajectory — flat-lining at the launch peak vs. continued growth
Release cadence — tagged versions or only main
Author bandwidth — solo project, employer-supported, or community-maintained?
Platform breadth — single-OS alpha vs. broadening
Stability claims — has the README dropped the "alpha / not for production" warning?
Competitor consolidation — has the obvious incumbent absorbed the idea or shipped a comparable feature?

A tool that fails most of these after 6–12 months is almost certainly dead and should be retired from the watchlist.

Current entries

Tool	Watching for	Next check	Reason
codealmanac	macOS-only (`launchd`-bound), requires Codex or Claude Code, YC S26 startup with a hosted-product path not yet visible, lifecycle agents run unattended with broad non-interactive filesystem access	2026-10-19	Transcript-harvesting plus a scheduled gardening pass is the right shape for a codebase wiki and the two ideas are worth stealing regardless. Want to see a Linux port, whether the unattended-agent trust model survives contact with users, whether the `almanac/` boundary gets a real sandbox, and what the business model turns out to be.
openhuman	Self-declared early beta with 170 open issues, enormous scope (memory + orchestration + workflows + meetings + messaging + voice + media gen + agent payments) in one app, nine-day GitHub trending run is launch-hype signal, GPL-3.0 unlike the rest of the toolbox	2026-10-19	Rust core with Privacy Mode enforced in-core plus plain-markdown memory makes the local-first claim more credible than most, and tinyagents/tinyflows being separately open-source means the durable parts may outlive the app. Want to see the scope narrow or the quality hold, issue count come down, contributors beyond the founding team, and whether Privacy Mode survives audit.
freeink	freeink-sdk is seven weeks old (2026-06-03) with 38★ against CrossPoint's 6.2k; de-link has no license file and no push since 2026-04-21; the hardware-abstraction claim is unproven off the boards it was extracted from	2026-10-19	"New devices are data, not code" is the right bet for e-paper firmware and the whole-stack openness (SDK + firmware + KiCad + BOM) is rare. Want to see the SDK drive a controller family GoodDisplay didn't make, de-link get a license and resume commits, and whether CrossPoint's userbase follows the generalization or stays on the device-specific firmware.
superhq	macOS-only alpha, three-week-old repo (2026-04-04), explicit "not production-ready," AGPL-3.0 single-vendor	2026-07-24	Auth gateway design is genuinely novel; want to see if it survives past the launch hype and broadens beyond Apple Silicon. shuru-sdk underneath is the more durable half.
gova	Two-day-old repo (2026-04-22), single author, no tagged releases, pre-1.0 API, Fyne fallback on Windows/Linux	2026-07-24	Explicit-Scope reactivity for Go GUI is a genuinely novel ergonomic bet; want to see if Windows/Linux get native integrations and whether the API settles before committing.
stash	One-day-old repo (2026-04-24), single author (established Go dev with 247 repos), three v0.x releases in first 24h, stages 4–9 of consolidation pipeline (causal/goals/failures/hypotheses) unproven in real use	2026-07-25	Nine-stage consolidation pipeline goes substantially further than hippo-memory / mempalace; want to see if the higher-order stages produce useful output or just thrash, and whether anyone besides the author ships a non-trivial integration.
atomicapp	Five-month-old repo (2025-11-25), single author, SQLite-only datastore (not plain markdown on disk), 1.3k stars in 5 months, very active	2026-07-25	The LLM Wiki pattern shipped as one binary instead of bolted onto Obsidian. Want to see if Ken sustains the velocity, whether contributors arrive, and how data export / migration holds up since you can't grep your way out of a SQLite-only store.
lfk	Six-week-old repo (2026-03-15), single author, pre-1.0 (v0.9.30), 320 stars, 30 releases in six weeks, no v1 commitment yet	2026-07-26	k9s alternative with a genuinely different navigation model (Miller columns + owner-based hierarchy) and built-in ArgoCD/Argo Workflows/Helm/KEDA/External Secrets integration. Want to see if release cadence holds, whether v1.0 ships, and whether a second contributor appears.
vera	Ten-week-old repo (2026-02-22), single author (Alasdair Allan), pre-1.0 (v0.0.127, 127 releases), 261 stars, deliberately anti-ergonomic design (no variable names)	2026-07-29	Genuinely novel design bet — typed De Bruijn slots + mandatory contracts + Z3 verification, all aimed at LLM-as-author failure modes. Want to see if anyone besides Allan writes nontrivial Vera, if VeraBench gets independent reproductions, and whether the verified-MCP-server milestone lands.
goose-relay-vpn	New repo by single author (kianmhz), CLI-only (no Android/iOS yet), Persian-speaking-market focus, AES wrapper unaudited	2026-07-29	Architecturally cleaner than masterhttprelayvpn (end-to-end AES, Google sees no plaintext) but trades the appeal "no infrastructure required" for a $4/month VPS. Want to see if independent contributors arrive, mobile clients ship, the AES integration gets reviewed, and whether the threat model holds against Iran's TSPU-equivalent.
bluetui	One-day-old repo (2026-05-01), zero stars, single author, Russian-only README, no tagged releases, packaging is `pip install -r requirements.txt` + shell wrapper	2026-08-02	Real Bluetooth HID remote for Smart TVs (Profile1 with UUID 0x1124, raw L2CAP on PSM 17/19, Consumer Control + Keyboard descriptor) is a genuinely unusual implementation; rest of the BT manager is utility. Want to see if anyone else lands a PR, packaging tightens (PyPI), README gets translated, and TV compatibility expands beyond the author's TCL test.
openwarp	Three-day-old fork (2026-04-29), 422 stars on momentum, single-vendor (`zerx-lab`, no other notable repos), no public release binaries, "early development" banner on the site, must `cargo build --release` from source	2026-08-02	Warp's first credible BYOP fork — the genai-based 6-native-protocol layer with reasoning passthrough is genuinely better than an OpenAI-compat shim, and AGPL/MIT mirroring upstream keeps it merge-able. Want to see if a binary release lands, whether `zerx-lab` actually keeps up with upstream Warp's release cadence, and whether a second contributor appears before the launch hype dissipates.
agent-skill-linter	Three-month-old repo (2026-02-12), 2 stars, single author (William-Yeh), no editor integration / pre-commit hook, depends on the cross-harness "Agent Skills" registry (`agentskills.io`) catching on	2026-08-02	The deterministic-lint-for-skill-publishing instinct is right (same argument as impeccable's detector); 21-rule scope is well-chosen. Want to see if `agentskills.io` registry adoption picks up, if a second contributor lands, and whether the linter expands past Python skills (deeper rules currently Python-only).
acai	Single-author org (~13★ across cli/server/docs), all repos created in last 2-3 months (CLI 2026-03-22, server 2026-02-27), CI/CD wiring still roadmap, hosted dashboard is the review surface with no published business model ("free forever maybe")	2026-08-03	The ACID convention (numbered acceptance criteria referenced from code) has legs independently of acai.sh, but the toolkit itself depends on the hosted dashboard for review. Want to see a notable third-party project adopting `feature.yaml` publicly, the CI hook examples landing, a second contributor in the org, and the hosted/self-hosted business model clarified.
surf	Single-author project (1.7k★) tracking browser TLS/QUIC fingerprints; viability hinges on keeping pace with Chrome/Firefox releases and uTLS upstream; non-idiomatic `g.Result` API from `enetx/g`	2026-08-04	Bus-factor-1, browser-version treadmill (Chrome ships every ~4 weeks, uTLS lags), unusual API. Want to see if a second maintainer arrives, fingerprint coverage holds against current Chrome/Firefox, and whether the Result-type dependency stays optional.
tweakcc	CC version-coupled binary patcher; whether Anthropic ships CC versions tweakcc can't keep up with, and whether Piebald keeps maintaining it	2026-08-04	Patches a closed third-party CLI — value evaporates the moment upstream changes outpace patches. Single-vendor maintenance bus factor. Want to see how the patch set tracks new Claude Code releases and whether the LIEF-based native-binary path holds.
oh-my-pi	Single-maintainer fork (Can Bölük) tracking upstream Pi (Mario Zechner's pi-mono); risk of bitrot if maintainer bandwidth drops	2026-08-04	Batteries-included counterpoint to Pi's minimalism. Want to verify sync cadence with upstream, whether the bundled tools (LSP, IPython, browser, SSH, multi-model role routing) drift from pi-mono, and whether a second contributor appears.
tilde-run	Closed-source SaaS in private preview, no published pricing, single vendor; container-level (not microVM) isolation; homepage was carrying a prompt-injection payload at ingest	2026-08-05	Transactional commit/rollback for agent runs is a genuinely useful framing and the only product I've seen ship it as managed infrastructure. Want to see GA pricing, threat-model statement, whether self-host is on the roadmap, and whether the "agent-first RBAC" claim survives third-party scrutiny.
agent-skills-eval	Four-day-old repo (2026-05-06), single author (darkrishabh), 257★ at ingest, MIT, TypeScript-only, costs scale 2× per iteration	2026-08-10	The `with_skill` / `without_skill` baseline split is the right methodology for measuring skill lift, and spec compliance is honest. Want to see contributor count, whether judge-flakiness mitigation patterns emerge, integration with the rest of the agentskills.io ecosystem, and whether the agentskills.io spec stays stable enough for tools at this layer.
routing-run	New service (no track record), license claimed open-source but repo not linked from homepage, per-request pricing only beats per-token at large context sizes, "zero logging" is a contractual claim	2026-08-10	The per-request pricing model and OSS-routing-infrastructure claim are differentiators if both hold. Want to see the actual repo, customer references, whether per-request economics survive OpenRouter's pricing evolution, and a privacy posture worth verifying.
re_gent	Pre-v1.0 (POC-completeness per README), 265★ at ingest, Apache-2.0, Claude-Code-only today, planned features (rewind/fork/multi-tool) not built	2026-08-10	Per-prompt agent VCS solves a real problem named in agent-principal-agent-problem. Want to see v1.0, Cursor/Cline adapters, integration with PR review tooling, second contributor, and whether other coding-agent ecosystems ship comparable provenance primitives that obviate it.
floci	Young project (org `floci-io`), Docker image just renamed `hectorvent/floci` → `floci/floci`, riding the LocalStack-Community-sunset moment, several services still stubs (Bedrock, Textract), fidelity is best-effort	2026-08-10	Genuinely fills the gap LocalStack Community left in March 2026 — MIT, no auth token, broader service coverage, real-Docker-container fidelity for stateful services. Want to see contributor count beyond the founder, release cadence, whether the "drop-in LocalStack replacement" claim holds across real init scripts, and whether the stub services get filled in.
gosentry	Day-of-announcement Go toolchain fork from a single security firm (trail-of-bits); must track upstream Go releases on an ongoing basis; LibAFL runner adds a Rust toolchain to the build env; bug-find list so far is L2/crypto-shaped	2026-08-12	"Same harness, stronger engine" is the right framing for a fuzzing fork — backward-compatible with `testing.F`, plugs Go's four worst gaps (path constraints, struct/grammar inputs, Go-specific bug classes, reporting). Want to see upstream-Go-tracking cadence, second contributor outside ToB, whether the LibAFL integration survives Go's quarterly toolchain churn, and whether anyone reproduces the bug finds on non-L2 codebases.
mnemonik	Young project (single-vendor `mnemonik-xyz`), Solana + Arweave hard dependency in `full` mode, embedding choice commodity (TurboQuant + default ONNX), monetisation surface unclear past free local mode	2026-08-13	Verifiable-memory framing fills a gap the recall-side memory tools (hippo-memory / mempalace / stash) explicitly don't address. Want to see if anyone outside the team ships an integration, whether the COSE/blake3/Ed25519 + Solana anchor flow holds up under audit, and whether the embedded recall quality keeps up with dedicated retrieval tools.
statewright	New repo (88★), single-team launch, Rust engine open-source under Apache-2.0/FSL but managed cloud is the review surface, advisory enforcement on Cursor only, research validation is a 5-task SWE-bench subset not the full 2294	2026-08-13	State-machine guardrails for agents are a clean structural answer to flailing-on-too-many-tools failure modes — the 2/10 → 10/10 SWE-bench-subset numbers on local models are the strongest evidence in the wiki for tool-space constraint as the lever. Want to see contributor count, whether the engine sees non-cloud adoption, full SWE-bench reproduction, and whether the managed-cloud / self-hosted balance settles.
needle	26M-param model from single team (Cactus Compute), four days old at ingest, single-shot function-calling only, English-only by training, finetuning is the recommended path	2026-08-13	The Simple Attention Network shape (no-FFN encoder, ZCRMSNorm, gated residuals, shared embed/output) is a real research contribution that ships with weights and a finetuning pipeline. Want to see if anyone outside Cactus ships finetuned checkpoints, multilingual or multi-turn variants land, and whether the 6000/1200 toks/sec numbers transfer off the Cactus runtime.
crofai	Single-domain hosted LLM provider with no observable track record, closed-source backend, Q4_0 baseline quantization on production models, public pricing page is the only documented surface	2026-08-13	Quantization disclosure as a column is genuinely useful and the prices are low. Want to see third-party usage reports, whether quality complaints surface on the aggressive Q4_0 baselines, sustained catalog updates, and whether the "cheapest" claim holds against repricing rounds from DeepInfra / Fireworks / Together.
forgezero	Two-month-old repo (2026-03-15), single author (alexvoste), 5 stars, macOS "in progress" and Windows "experimental," aggressive 1.5→1.9 release cadence in two months suggests pre-adoption iteration	2026-08-19	Strict-warnings-and-sanitizers-by-default + pre-link symbol check is a genuinely opinionated bet on a niche (assembly + bare-metal C) most modern build tooling ignores. Want to see a second contributor, macOS/Windows parity, whether the no-escape-hatch strict defaults survive real user pushback, and whether the project finds an audience beyond hobbyist OS-kernel writers.
pve-microvm	v0.3.12, single author (Rui Carmo), ~320 stars, Proxmox-only, structurally coupled to patching upstream `qemu-server` Perl internals it doesn't control (every PVE upgrade can break it)	2026-10-18	Genuinely useful "container-speed VMs with actual isolation" on a homelab node, and the host-provided-kernel / OCI-rootfs design is clean. Want to see whether the version matures past 0.3.x, a second maintainer appears, the QEMU-10.x MMIO-for-Linux and GPU/vIOMMU-passthrough gaps get contributor patches (Carmo is explicitly asking), and whether any upstreaming to Proxmox happens.
lazypi	v0.6.3, single author (Rob Zolkos), ~373 stars, MIT, value is pure curation over a fast-moving third-party Pi package ecosystem it doesn't control	2026-10-18	The LazyVim-for-Pi installer (vs oh-my-pi's fork) is a clean answer to "vanilla Pi ships empty," and it's the best evidence Pi's community-package bet worked. Want to see whether it gains a second maintainer, whether the curated catalog stays fresh as packages come and go / get abandoned, and whether Pi's ecosystem keeps growing enough to justify a curation layer at all.
xslang	Single-author project at v1.2.32, limited public history; ambitious cross-target claims (Linux/macOS/Windows/WASI/iOS/Android/ESP32) need real-world validation; site doesn't make license obvious	2026-08-21	Single 2.9 MB binary containing the whole toolchain (JIT + LSP + debugger + REPL + transpilers) across that many targets is unusual together. Want to see external adoption (any non-author projects), iOS/Android/ESP32 claims under real scrutiny, a clearly stated license on the site, and whether the JIT/VM benchmark numbers hold against fresh comparisons.
freenet	From-scratch Rust rewrite of Freenet (formerly Locutus); production adoption signal is the demo network, not dApps with users; small team funded by grants/donations	2026-08-22	Small-world-ring + browser-served decentralized apps is a structurally different bet from Tor / Yggdrasil / IPFS, and the new Freenet has shipped a working network plus developer manual. Want to see any non-demo dApp with users, contributor count beyond core team, and stable funding past the current grant footing.
sandbox-agent-sdk	Built on Docker's undocumented `sandboxd.sock` API which can break in any minor release; macOS/Windows-only because Docker Sandboxes is; production signal not yet visible	2026-08-22	Lets you escape Docker Sandbox's six-agent whitelist and run arbitrary containers behind microVM isolation — the actual unlock people will want. Want to see whether the upstream API stays stable, second contributor, integration patterns beyond the demo agents, and whether Docker formalizes the API surface.
kata	Early public preview, no tagged release yet, command contracts explicitly unstable, 210★, no auth in local or remote mode, import always recreates the DB	2026-08-22	The keep-issues-outside-the-repo bet (vs. beads' Dolt-in-repo) is a clean alternative for non-git or clean-footprint workflows. Want to see contracts stabilize into a tagged release, a second contributor, and whether the planned shared-server mode ships with actual auth. Part of the kenn-software-suite.
msgvault	Self-described alpha (v0.14.x), README warns storage format and CLI flags may change without notice; 1.8k★, single-vendor (Kenn Software)	2026-08-22	The SQLite-for-store + DuckDB-for-analytics split is the right shape for lifetime-email archival and the vector/hybrid search is genuinely useful. Want to see the storage format freeze, the alpha label drop, contributor count beyond the vendor, and whether incremental Gmail History sync holds up over very large mailboxes. Part of the kenn-software-suite.

| mindwalk | Cross-session cumulative history; adapters beyond Claude Code/Codex; whether the spatial view beats a text diff | 2026-10-16 | Single-author, brand-new (July 2026), value proposition still contested on HN | | zerofs | WAL / multi-writer support; release cadence; second contributor | 2026-10-16 | Single-author young storage project; single-writer, no WAL yet; author-written benchmarks | | reaction | External security audit + sustained activity | 2026-10-16 | Single maintainer (ppom), no audit, Linux-only, young v2 Rust rewrite; runs as root wiring firewall rules | | gap | fred integration / graduation from jam proof-of-concept; macOS support | 2026-10-16 | Experimental single-author jam project; the diff engine is meant to live inside fred, not ship standalone | | commonforms | Second maintainer + a clear/standard license; dataset-prep code leaving WIP | 2026-10-16 | Single-author repo (Joe Barrow), depends on the FFDNet models, custom NOASSERTION license |

| moonstone | 1.0 release, Windows support, real-world adoption vs Lux/Nix | 2026-10-16 | Young single-author Zig project, POSIX-only, pre-1.0 with shifting APIs | | flint-chart | API stabilizing; Python package release; token/correctness benchmarks | 2026-10-16 | Early Microsoft Research release, evolving JSON spec, unreleased Python port, no benchmarks yet | | kastor | Second codegen target + first real hosted-platform provider beyond in-memory | 2026-10-16 | Early proof of concept, single author, 57 stars; only LangGraph codegen + in-memory target work today | | sp4rk | First tagged release + adoption beyond the author (0 stars, README says early alpha) | 2026-10-16 | Pre-release, single-author (v0lka), APIs may change without notice | | showagent | Star traction, release cadence, second maintainer | 2026-10-16 | Single-author, early (34 stars); promising cross-agent session conversion but unproven | | dockerscan | v2.1 offensive/registry features shipping; license terms staying usable | 2026-10-16 | Single-author; proprietary source-available license (not OSS), commercial-competitive use restricted | | tc-lang | ~40 stars, single author (Alonso VM), pre-1.0, MIT README badge but no SPDX license file detected by GitHub, "make an OS with it" aspiration | 2026-10-19 | Transpile-to-C11 minimalist systems language with genuinely unusual ergonomics (strun, fat pointers, host/DLL hot-reload, async channels). Want to see a second contributor, whether stage1 self-hosting happens, the license clarified, and any users beyond the author. | | kanbots | New product, open-core, no public source repo (landing page only), desktop-app maturity unproven, single vendor | 2026-10-19 | Worktree-per-card parallel-agent kanban with cost caps and decision-gating is a clean framing. Want to see adoption, whether the OSS build really ships all features, contributor count, and whether the open-core split holds. | | claude-code-workflow-creator | 85 stars, single author (Ray Amjad), no LICENSE file, depends entirely on Claude Code's unreleased env-gated Workflow tool (CLAUDE_CODE_WORKFLOWS=1) | 2026-10-19 | The deterministic-JS-orchestration model matches how the unreleased Workflow tool actually works. Want to see whether Anthropic ships the tool publicly, whether the skill tracks the released API, a license appearing, and a second contributor. |

Graduated

(none yet)

Abandoned

(none yet)