Skip to main content
Taskbean has two product surfaces backed by one local data model. Both surfaces use ~/.taskbean/taskbean.db. Set TASKBEAN_HOME to move the Taskbean data directory or TASKBEAN_DB to override the database path.

​
Identity and attribution

A Project is logical. A Workspace is physical. Multiple checkouts, worktrees, and forks can roll up to the same Project. The Project ID is the durable internal identity. Taskbean uses an owner/repo Project Key for Git-backed work, preferring upstream over origin. If a repository is renamed or transferred, the Project keeps its Project ID, adopts the new Project Key, and keeps the old key as a Project Alias. An Agent Session without a local path can use a Remote Workspace only when repository metadata or a known Project Alias resolves one Project without ambiguity. Otherwise, it remains Unassigned Work. Repository identity establishes Project membership, but stable lineage evidence is required before Taskbean merges a Remote Workspace with a local Workspace. Read the glossary before designing integrations that create or resolve Projects.

​
Independent versions

The CLI, desktop app, and Agent Skill can version independently. Use bean --version for the CLI and GET /api/version for the app. Follow GitHub releases instead of relying on a hand-maintained version table.

​
Platform boundary

The CLI package and compiled binaries target Windows, macOS, and Linux. The current desktop app dependency set includes Windows ML, WMI, PDH, Windows toast notifications, and PowerShell protocol registration. Treat those app capabilities as Windows-specific unless current source proves otherwise.
Last modified on August 12, 2026