Skip to main content
Sign inDownload

Version control

Review what changed in your workspace: imports, enrichments, schema updates, and view edits. Appenda records one bounded commit per meaningful job, not one line per row.

Workspace Version control lists durable activity across tables. Filter, export, and search help you scan imports, enrichments, and schema changes.

Overview

Version control is the activity feed for pipeline work you want to keep. Open it as a superior tab beside your tables, or open Table history on one table when you need the same feed scoped to that grid.

There is one history model: durable activity only. Layout tweaks on a view (filter, sort, column width, freeze) stay on the view and do not create commits.

Open workspace Version control

  1. Click Version control in the title bar (GitBranch icon, left of Agents).
  2. The superior tab opens with the workspace activity feed.
  3. Use Filter, Search, and Export in the toolbar to narrow or export what you see.
  4. Switch back to a table tab to keep editing rows.

The tab stays open while you move between tables until you close it.

Table history

When you are focused on one dataset, open the History rail from the table toolbar (clock icon, left of Run). It shows the same commit shape, filtered to the open table.

See Table history for rail steps and row details.

What appears in history

ActivityCommit shape
CSV importOne commit when the import job finishes
Enrichment runOne commit per approved batch on a column
List importOne commit when the search job ends
Row or schema editsBounded commits for meaningful batches
View create, rename, or deleteOne commit per view change

Bulk work never writes one commit per row or cell.

What does not appear

These stay on the active view or device and are not version history:

  • Filter and sort on the current view
  • Column width and show/hide
  • Column freeze (device-local)

Column reorder may still appear in older workspaces until product stops recording it. Restore and fork from a version are planned.

Read a commit row

Each entry includes:

  • Past-tense title — for example "Imported 847 leads" or "540 leads were enriched"
  • Timestamp — absolute local time
  • Actor and channel — Local user on Desktop UI, agent-as-user, API, or MCP
  • Short ref — workspace-unique id from the desktop app (the UI renders the stored ref only)

Enrichment rows show the provider logo and capability-style title. Schema adds and deletes use green or red accent strokes.

FAQs

Is there an All activity filter?
No. Version control shows durable workspace activity only. Ephemeral view layout is not mixed into the feed.
How is table history different?
Same commits, different scope. Table history filters to the open table. Version control spans the workspace.
Can I restore an older version?
Not yet. History is read-only navigation today. Restore and fork are planned.
Where does the short ref come from?
The desktop app stores a workspace-unique Crockford short id on each commit. The UI displays that field only.