Source Built from main · latest release v0.4.0

All terms

What each word in Deskfolk means, how it relates to the others, and the names it deliberately avoids. Split into seven topics.

On this page
  1. People and roster
  2. Sessions
  3. Collaboration
  4. Workspace
  5. Runtime
  6. Models and tools
  7. Approval and bounds

A single-person agent collaboration app running locally on macOS (with Windows and Linux as experimental previews): you hand a multi-day, multi-step job that needs rework to named, persistent Bots (one or several) and walk away; its files are kept by job and ticket in the workspace and open and take annotations in the app, every turn is drawn on the job's flow, and Bots look back after a delivery and improve their own memories and skills; the model does the work and the app holds it to account — your words are not lost, done has a definition, a stop is a state, and a supervisor chases what stalls. Those rules are code and do not change with a prompt; with the defaults hung on them they are one way of working: which of the app's own steps run and with what numbers is the engine, chosen per session, and an engine with no jobs, Plain, leaves all of it out but your approvals, stops and spend (ADR 0103); how Bots work is in the built-in prompts; you can change both, and Bots can propose prompt changes. Bots collaborate through directs, groups, mentions and asynchronous handoffs (modelled on Grok Bot); the computer is a shared folder on this Mac, not a cloud VM.

WIP: This document defines the domain language; it is not a statement that every capability has passed acceptance. Entries are written for macOS (Dock, Keychain, Finder, Trash); what stands in for them on Windows and Linux, and what those do not have yet, is in Windows preview and Linux preview. For the current scope, see the README; for the direction of work on the kernel of plans, tickets and done-when, and on full coverage of conversation operations, see the roadmap.

Terms by topic

One page per topic; click a term to jump to it.