Your First Session

A complete walkthrough of your first coding session with Broski.

Before You Start

Make sure you have everything ready:

Requirement	How to Check
Bridge running on your system	Terminal shows QR code and "Bridge listening on port 18274"
Phone connected	Green connection indicator in the app
AI backend configured	OpenCode or Claude Code with valid API key

Not connected yet?

Follow the setup guide first, then come back here.

Step 1: Open a Project

Go to the Projects tab

Tap the grid icon in the bottom navigation bar

Find your project

Projects from your system's home directory appear here. Scroll or use the search bar.

Tap to open

Tap on a project card to create a new session in that directory.

No projects showing?

The bridge scans your home directory for projects. Make sure your code is in a folder under~ (e.g., ~/Projects/myapp).

Step 2: Send Your First Message

Once you've opened a project, you'll see the chat screen. Here's how to interact with your AI:

Tap the input field

The text input is at the bottom of the screen. Tap to bring up the keyboard.

Type your message

Ask the AI to do something. For example: "What files are in this project?" or "Explain what this codebase does"

Tap send

Hit the send button (arrow icon) to submit your message.

Watch the response stream

The AI's response appears in real-time as it thinks and works.

Good First Prompts

"What is this project? Give me a brief overview."

Great for understanding a new codebase

"Find all TODO comments in the codebase"

Useful for identifying work items

"Add a comment to the main function explaining what it does"

A simple edit to see how file changes work

Step 3: Understanding Tool Calls

When the AI needs to do something (read a file, run a command, edit code), it uses "tools". You'll see these as cards in the chat:

Tool	Icon	What It Does
Read	Document	Reads file contents to understand your code
Edit	Pencil	Modifies an existing file
Write	Plus-document	Creates a new file
Bash	Terminal	Runs a shell command
Search	Magnifying glass	Searches for files or text
Task	Robot	Delegates work to a sub-agent

Tool Card Anatomy

Reading src/main.ts

Completed

Tap the card to expand and see details (file contents, command output, diff preview).

Step 4: Approve a Command

Some actions require your approval before they run. This keeps you in control:

Permission Required

The AI wants to run a shell command

npm install lodash

When do you need to approve?

• Bash commands: Running shell commands
• File edits: Modifying existing files (configurable)
• Destructive operations: Deleting files, git operations

For more details, see the Approving Commands guide.

Step 5: View the Results

After the AI makes changes, you can review them:

Viewing Diffs

When a file is edited, you'll see an inline diff:

src/main.ts+3-1

function main() {

- console.log("Hello")

+ // Initialize the application

+ console.log("Starting app...")

+ init()

}

Red lines with - are removed. Green lines with + are added.

Full-Screen Diff

Tap "View full" on any diff card to open a full-screen diff viewer with:

• Split view: Before (left) and After (right) side by side
• Unified view: Single column with changes marked
• Syntax highlighting: Colored code for readability

Undoing Changes

Don't like a change? You can undo it:

• Tap the "Undo" button on any edit tool card
• Or type /undo in the chat

Step 6: End the Session

Sessions are automatically saved. You can:

• Leave anytime: Just navigate away. Your conversation is saved.
• Resume later: Go to the Sessions tab to see all your conversations.
• Delete if needed: Swipe left on a session to delete it.

What gets saved?

• All messages (yours and the AI's)
• Tool calls and their results
• File diffs and changes
• Token usage statistics

Note: The actual file changes on your system are persistent - they're saved to disk as they happen.

You've completed your first session!

You now know the basics of using Broski to chat with AI, approve commands, and review code changes.