Agent has no access to previous Commits and branches

Problem
The agent currently has no visibility into previous commits or existing branches. This makes it impossible for users to reference earlier work, review recent changes, or continue modifying previously committed code.

Why this matters
Without access to commit history and branches, users:

• Cannot easily locate their latest commit
• Cannot review what changed in prior sessions
• Risk duplicating work or breaking existing logic
• Lose continuity across sessions

Suggested improvement
Grant the agent read access to:

• Previous commits on the active repository
• Available branches

Additionally, in each session, display the latest commits of the active branch in a dedicated section, including:

• Commit message / description
• Commit ID (hash)
• Timestamp

This would allow users to:

• Quickly understand recent changes
• Resume work on the correct commit or branch
• Review and modify existing code more safely and efficiently

The issue names no files or tests. Start by locating the session view and the active-repository data flow, then trace how repository information is exposed to the agent. Done means the agent can read existing branches and commits, and each session shows the active branch’s latest commits with message, hash, and timestamp.