Skip to main content

Version Control

Just about every aspect of a Plantic plan is version-controlled, and anything that can happen during a plan creates a new version in the plan's history. This includes:

  • Adding, removing, or updating context (when you do it manually or when Plantic does it automatically).
  • When you send a prompt.
  • When Plantic responds.
  • When Plantic builds the plan's proposed updates to a file into a pending change.
  • When pending changes are rejected.
  • When pending changes are applied to your project.
  • When models or model settings are updated.

Viewing History​

To see the history of your plan, use the plantic log command:

plantic log

Rewinding​

To rewind the plan to an earlier state, use the plantic rewind command:

plantic rewind # Select a previous state to rewind to
plantic rewind 3  # Rewind 3 steps
plantic rewind a7c8d66  # Rewind to a specific step

Preventing History Loss With Branches​

Note that currently, there's no way to undo a rewind and recover any history that may have been cleared as a result. That said, you can use rewind without losing any history with branches. Use plantic checkout to a create a new branch before executing rewind, and the original branch will still include the history from before the rewind.

plantic checkout undo-changes # create a new branch called 'undo-changes'
plantic rewind ef883a # history is rewound in 'undo-changes' branch
plantic checkout main # main branch still retains original history

Viewing Conversation​

While the Plantic history includes an entry for each message in the conversation, message content isn't included. To see the full conversation history, use the plantic convo command:

plantic convo

Rewinding After plantic apply​

Like any other action that modifies a plan, running plantic apply to apply pending changes to your project file creates a new version in the plan's history. The plantic apply action can also be undone with plantic rewind.

While previous versions Plantic would not also revert the changes to your project files, this is now the default behavior as of v2.0.0. If there are potential conflicts (i.e. you've made changes on top since applying), Plantic will prompt you to decide how to handle the conflict.

This behavior can be disabled if desired by setting the auto-revert-on-rewind config setting to false:

plantic set-config auto-revert-on-rewind false
plantic set-config default auto-revert-on-rewind false # set the default value for all new plans