Starting an interactive session

• Type your instructions or questions directly in the terminal
• Press Enter to send your message to Bob
• Bob Shell will respond with its analysis and suggestions
• For tool usage (like reading or writing files), you'll be prompted to approve or decline each action

Use the @ symbol to reference files in your project:

This tells Bob Shell to read and analyze the specified file before responding.

Type / to access a menu of available commands:

• Built-in commands like /help for assistance
• Mode-switching commands like /code or /ask
• Custom commands you've created

For a complete list of available commands, see Slash commands in Bob Shell.

When Bob Shell needs to modify files, it will show you the proposed changes:

• By default, changes are displayed in the terminal with a CLI diff view.
• To use an external editor for reviewing changes, configure your preferred editor with the /editor command. Then select the "Show diff in editor" option when prompted to review changes.

For security, Bob Shell requires your approval before:

• Reading files.
• Writing or modifying files.
• Executing commands.

You can approve or decline each action individually when prompted.

Bob Shell maintains context throughout your conversation, allowing you to:

• Ask follow-up questions.
• Refine previous requests.
• Build on earlier responses.

• Be specific in your requests to get more targeted responses.
• Use @ references to provide code context when needed.
• For complex tasks, break them down into smaller steps.
• Use slash commands to quickly access common functionality.
• When working with large codebases, direct Bob Shell to the most relevant files.

Interactive session works best for:

• Exploratory coding sessions.
• Debugging and troubleshooting.
• Learning new concepts or technologies.
• Tasks that require multiple back-and-forth exchanges.
• Projects where you need to review changes before they're applied.