Open Walnut

Connect a task to an agent session

Start with one project and one configured coding agent. Check how tasks, notes and session output are grouped before sharing access.

What it’s useful for

Open Walnut links a project’s tasks to the agent sessions doing the work. Notes and memory sit beside them in a locally run workspace. It is most relevant when a personal work system also needs to start and review coding sessions.

Inside the product

• Organize projects, folders, tasks and subtasks alongside notes and searchable memory.
• Open and review coding-agent sessions, files and per-session changes in a web interface.
• Use a local data directory and documented connections to separately configured agents or SSH hosts.

Good to know

• The core setup requires macOS or Linux and a configured coding agent; it is not a hosted Notion workspace.
• Notion database, formula, permission and import parity were not established.
• Local storage describes where records live. Check the selected model provider separately before assuming agent requests stay local.

The maker’s build notes

The official product metadata states that Walnut was built with Claude Code. Its repository separately describes using coding agents at runtime. Those are different claims: the first is maker-reported development attribution; the second explains the product’s operation. No local installation or agent run was performed here.

A few more details

Sources & maker notes

Build details come from the maker’s linked account. vibeforthat has not independently audited the code or tested every product function.

• Open Walnut — product scope and maker build attribution
• Open Walnut — maintainer repository