Configuration revision history

ArxDeck records an append-only revision history for configuration entities and knowledge items. Every successful save creates a new revision with a snapshot, actor, and source context. You can browse diffs and restore a prior snapshot — restore always creates a new revision; history is never rewritten.

Where to find History

Versioned resources include a History link in the detail page header actions. Open it to see chronological revision rows with metadata and summaries.

History is available for:

• Project and global agents, workflows, skills, scheduled tasks (definition and durable state on one timeline)
• Labels, ticket views, knowledge types, webhooks, content modules
• Project general settings (name and timezone only)
• Project templates
• GitHub settings (update_settings, set_ci_workflow revisions)
• Publish / deployment settings (application config, auto-deploy, staging, secret metadata — never raw secret values)
• Feedback settings

Knowledge items keep their existing History tab and Knowledge → Recent changes browse route. Both read from the same underlying revision system.

Change trail

Each revision row shows a human-readable change trail:

• Actor — user, agent, or system display name
• Source — how the change was applied (manual edit, approved proposal, chat, agent run, restore)
• Links — optional links to the originating proposal, chat conversation, or agent run
• For approved proposals, the proposing agent appears as secondary context

Use View diff for text and field changes (side-by-side modal with line-level highlighting). Array-only changes show compact inline +/- summaries.

Restore

Restore reapplies a prior snapshot as a new revision. You need the same permissions as editing the resource. Restore does not delete intermediate revisions — it appends a new row labeled as a restore.

What is excluded

These operations do not create configuration revisions:

• Project capability toggles (enable/disable feedback, Publish, etc.)
• Feedback item triage (status changes on individual feedback rows)
• Ticket draft, comment, and relationship proposals (separate proposal flow)
• GitHub binding, OAuth, inject, and validate operations
• Deployment enable, disable, promote, runs, validate, repair, and mode migration

MCP and API

Configuration revision history is UI-only in v1. There are no MCP list_*_revision or get_*_revision tools for agents, workflows, skills, or other config entities yet. Knowledge items continue to expose revision tools via MCP (list_knowledge_item_revisions, get_knowledge_item_revision).

Related

• Knowledge base — item history and Recent changes
• Chat & proposals — how approved changes reach History
• ArxDeck Helper — proposals that become revisions after approval