Inside Bits: make the permission boundary visible before the agent stays on
A 22 October Product Hunt launch and an MIT maintainer repository show how durable tasks, local memory and explicit policy files can make an agent easier to reason about.
Bits appeared at #17 on Product Hunt's daily leaderboard for 22 October 2026 with 83 points when checked 23 October. Its product page showed 64 followers at that check. Those are dated launch-day discovery signals, not market share, a final lifetime total or evidence of reliability.
Documented components, not a complete production inventory.
- Daemon + crash-safe turns
- Documented background runtime and durable task state
- Markdown memory + SQLite FTS5
- Documented local memory files and search layer
- Web, desktop + shared protocol
- Documented interfaces and common protocol package
- MCP connectors + secrets + policy files
- Documented integration and control surfaces; not independently security-tested
A recent launch with a bounded popularity signal
Product Hunt's dated 22 October 2026 board lists Bits seventeenth with 83 points. The launch presents a local-first personal agent. FreeStack reviewed that launch page and the current maintainer repository. We have not installed Bits, connected an account, run a task, inspected network traffic or verified the maker's reliability claims.
What the maintainer actually publishes
The repository documents a background daemon, crash-safe turn persistence, Markdown memory under ~/.bits, SQLite FTS5 search, a web app, a desktop app and a shared protocol package. It also describes model-provider support including local routes through Ollama or LM Studio, MCP connectors, encrypted secrets and policy files. The source is MIT-licensed and currently requires Node.js 24 or later plus pnpm. These are documented components, not a complete inventory of any hosted service.
Durable work needs a visible state boundary
Bits separates a persistent daemon from its interfaces and records tasks and memory locally. FreeStack's editorial lesson is to name what survives a restart before giving an agent more access. A durable queue can be useful, but persistence also makes stale context, repeated actions and unclear recovery more consequential. Record the input, current stage, approval status and safe resume point in terms a person can inspect.
Connectors do not replace permission design
The project documents MCP connectors, encrypted secrets and policy files. Those features can support a safer design, but their presence does not prove a connector is correctly scoped or a task is harmless. Treat every read, write, command, network request and credential use as a separate capability. Start with dummy data and deny actions that the first routine does not require.
Try the smaller learning workflow
FreeStack suggestion, not Bits' production stack: use the linked guide to plan one read-only weekly routine with Excalidraw and VS Code. Draw the input, local memory, draft output and human approval. Classify possible actions as allow, ask or deny, then specify the failure record. Save that two-tool toolkit to a private stack. The exercise teaches the boundary without installing Bits or claiming a working automation.
Where the free boundary changes the plan
The MIT repository provides an ongoing free software route, but it does not include hardware, hosted models, external APIs, managed uptime or support. FreeStack editorial upgrade triggers are concrete: pay when a specific approved model, hosted connector, team governance requirement, audit history or service level is worth more than operating it yourself. Do not buy an agent membership merely to store a workflow that can be written and reviewed on one page.
Sources & further reading
Follow the source for current details. Product Hunt is used for discovery and launch history; technical claims use provider documentation or the project repository.