Chat, tasks, rooms
Treat folks like teammates and keep each run under control.
Folks and tasks
A folk is a durable identity. A task is one conversation with that folk — its own transcript, engine session, approvals, costs, and state.
Use a new task when you want fresh context without duplicating the folk. Messages sent while a folk is busy are queued. Supported engines can be steered mid-turn.
Rooms
Rooms put several folks in one conversation. Each participant keeps its own engine process. Room timeouts stop one participant from blocking the group forever.
Handoffs
Folks can hand work to other folks. Delegated runs report completion, failure, and cancellation back into the parent thread.
Edits and branches
Editing an earlier message starts a new path. OpenFolks does not resume a stale engine session after a rewind, so the next turn follows the visible branch.
Memory and folders
Folk memory is visible and editable. A folk may have a dedicated working folder; rooms can share one. Cloud workspaces use a stable default so generated files stay findable across tasks.