Support & Documentation

Frequently Asked Questions

How Codestory View fits into your Git workflow.

Using the Visualizer

It is a companion. Codestory View is a graphical interface for the Codestory CLI. It gives you a visual dashboard to review and approve changes before they happen. You must have cst installed for the Visualizer to work.

No. Continue using SourceTree, GitLens, or the terminal for pushing and merging. Codestory View is a specialized tool solely for splitting and grouping your messy work-in-progress into clean commits.

No. The Visualizer handles the cst flags for you. You can adjust parameters like model temperature, cluster strictness, and intent using simple sliders in the sidebar.

Safety & Undoing

You remain in control. The Visualizer shows a Graph Simulation (a preview of the history). If you don't like it, tweak the slider and click Re-run. Nothing is written to your actual Git history until you explicitly click confirm.

The Visualizer runs a dry-run first. If a proposed commit fails safety checks (like syntax errors), you will see the graph snap back to the original state. This visually confirms that the operation was aborted and your repo was protected.

AI & Logic

Yes. Click on any commit node to inspect it. The interface highlights the specific code blocks (called mechanical chunks) included in that commit and displays the intent (the AI-generated message) that links them.

Ready to master the visual workflow?

Learn how to interpret the graph simulation, configure cluster strictness, and use the safety revert to its full potential.