Frequently Asked Questions

Everything you need to know about Codestory View and how it fits into your development cycle.

Is Codestory View a separate tool from the CLI?

It's a companion. Codestory View is a clean, visual interface for interacting with our CLI. It adds other handy features like a semantic search for commits and an easy way for you to manage many projects in one unified place.

Does the Visualizer replace my current Git client?

No. Continue using SourceTree, GitLens, or the terminal for pushing and merging. The Codestory View & CLI are designed for managing your commit history. Once you're done, you can continue using whatever you were using to push your changes.

Do I need to know the CLI commands to use it?

No. The Visualizer handles the cst flags for you. You can adjust parameters like model temperature, cluster strictness, and intent using an intuitive config manager.

How do I know the split won't break my build?

The visualizer/CLI are “index-only”. This means that only the “recording” of your project history is changed. None of your files are touched!

Can I see why the AI grouped certain files together?

Once you finish running a command, click on any of the new commit nodes to inspect it. The interface shows you the specific changes included in that commit and the newly generated commit message explaining why those changes happened.

Still have questions?

Check out our full documentation

View Docs →