Skip to main content
The Git panel lives alongside chat, Ask, and the terminal so you can move from idea to commit without losing context. Here’s how to weave it into your everyday flow.

Start with a Goal

  • Outline your plan in chat and reference the files you expect to touch.
  • As you or the assistant edit code, keep the Git panel open to monitor what changed.
  • Drag updated files from the Git panel into chat when you want explanations or further modifications.

Use Ask to Investigate Before You Edit

  • Run Ask Your Codebase to understand the current behavior of a module before you refactor it.
  • Add the referenced files straight to chat or the Git panel so they stay visible while you work.

Stay Organized While You Iterate

  • Commit early and often. Small commits make it easier to reason about what changed.
  • Pause a half-finished idea by stashing the related files. Pop the stash when you return to it.
  • If you want to explore a different solution, branch off from the current conversation and create a new Git branch at the same time. Give them matching names so you can recognize the pairing later.

Keep Remote Workflows Smooth

  • Pull at the start of the day and before you push to avoid surprise merge conflicts.
  • Use the branch comparison view and the Review button to sanity-check your work before opening a pull request.
  • Share the review chat with teammates; it captures the AI summary plus any follow-up questions you ask.

When You Need the Terminal

  • The Git panel covers the most common actions, but some tasks—like rebasing or editing submodules—still require the terminal.
  • Run those commands in Mistle’s built-in terminal. The panel refreshes automatically after the command finishes, so you never lose track of the state of your working tree.