Agents

The same graph, reachable without a browser.

• verified A REST API over the graphpersona: keys /features/
• verified API tokenspersona: keys /help/connect-other-apps-api
• verified An MCP serverpersona: keys /help/mcp-server
• tested A command line clientpyflow tree, add, done, rm, find, remember, recall, share, export. The same API and the same token as the browser and the MCP server, zero dependencies, and --json on any command for piping. test/e2e/cli.mjs runs the actual binary in a child process against the deployed site, with nothing but environment variables, the way a cron job would. It found that every id the tool printed was shortened and no command accepted one, so its own output could not be piped into its own next command. Held at tested rather than verified on purpose: verified means a panel persona drove it, and a shell client is not something a browser persona can hold.test/e2e/cli.mjs /help/cli
• tested An agent writes through the same mutation queue as the UI pandoPando axiom 3: there is one way to change the graph. test/writepath.test.js asserts every write that changes an outline goes through applyBatch, that a bearer token and a browser session become one actor, and that the permission check rides on the queue rather than on the route. The writes that cannot be mutations - signing in, deleting an account, creating an agent - are enumerated with a reason each, and a new one is red until somebody writes down why.test/writepath.test.js
• verified Capture one line into the inbox in one request pandoA URL, not a native app per platform: a phone shortcut, a Siri phrase, a widget, a cron job or curl all reach it and nothing has to be installed. The inbox is an ordinary bullet with a flag, made on first use, so emptying it is deleting bullets.persona: keeping blog 2026.02, 2026.05