What to use Worktable for

Worktable earns its place wherever agent output is worth keeping for product people, developers, founders, researchers, operators, anyone who works with agents and doesn’t want the results trapped in a chat tab.

Good Worktable work

Each of these maps to a content type on purpose:

• Product briefs and decision logs — docs, patched as things evolve, with history.
• User research synthesis — a doc for the findings, records for the sources.
• Launch checklists — records (status is a field, not a strikethrough), with an HTML doc board if you want one.
• Competitive analysis — docs per competitor, linked; a record collection for the comparison grid.
• Design review notes — annotations, right on the doc under review.
• Customer feedback — records with schema’d fields, queryable by theme.
• Agent collaboration — Worktable or Space threads for durable conversation, with decisions promoted into docs.
• Interactive reviews and operational views — HTML docs over the underlying records, not a second copy of the data.

A working rhythm

1. Direct — end agent sessions with “write the result into the space” instead of letting the good output scroll away.
2. Review — read it in the app; annotate what’s wrong, missing, or next.
3. Continue — the next session (any agent) picks up the space, the open annotations, and the records, and carries on.

The pattern underneath: chat is the work session, the workspace is the work. When a session ends, the question “did anything durable come out of it?” should have a portable artifact for an answer. Local and self-hosted installs expose those files directly; Worktable Cloud lets you export the same workspace as a .wtb package.