[Feature]: More visibility about the branch from which container-use starts

[marcindulak]

What feature would you like?

Sometimes I find container-use is working (creates an environment) starting from a random branch.
When I ask Claude about it, it says something like "Yeah, I started working from some other branch".

So I added rules like the ones below to ~/CLAUDE.md, but since it's an LLM, it anyway does not obey these rules from time to time.
Maybe there is a better way to enforce the work on the latest code from the current branch, and provide a visibility to which branch container-use is working on?

# rule compliance verification

You MUST start every response by stating:
1. "Applicable CLAUDE.md rules: [list specific rule sections]"
2. "Branch I'm working from: [branch name]"

You MUST stop and ask for guidance if you notice yourself about to violate any CLAUDE.md rule.

# environment creation                                                                                

When creating container-use environments, you MUST:
1. Always create from the currently active branch, NOT from a specific named branch
2. NEVER specify a specific branch name or `main` unless explicitly instructed

You MUST NOT assume which branch contains the latest changes. Always start from the current working branch.
You MUST use the local "git branch" command (outside of any environment) to check the current branch.
This is the ONLY case you can use local git, otherwise ALL operations MUST happen in an environment.

Why would this be useful?

To avoid mistakes of starting work from a wrong branch.