Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Remote] Assistant sessions display the wrong workspace and branch

Open
#2,360 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
frontend, web-dev

Research direction

Reproduce this in the BitFun Remote web UI by selecting a normal workspace, switching to Assistant mode, and opening a Claw session. Trace how the session header retains workspace and branch state; done means the assistant context is shown or repository fields are omitted, without changing normal workspace behavior.

Written by the indexing model from the issue text.

Description

bug

Bug

When opening a Claw assistant session in BitFun Remote, the header displays home / master.

Expected behavior

Assistant/Claw sessions should show the assistant context, or omit repository workspace and branch information when no Git workspace is attached.

Actual behavior

The remote web UI keeps displaying the previously selected normal workspace (home) and its branch (master). This is misleading, although command execution appears to use the correct assistant workspace.

Reproduction

  1. Open BitFun Remote with a normal workspace selected.
  2. Switch to Assistant mode.
  3. Open a Claw assistant session.
  4. Observe the session header: it still shows the normal workspace and branch.

Environment

  • BitFun 0.2.17
  • macOS desktop client
  • BitFun Remote web UI via relay

Additional evidence

The Claw session target is the dedicated assistant workspace (~/.bitfun/personal_assistant/workspace), which is not a Git repository. The desktop runtime logs also report that assistant session commands use that path, so this appears to be stale web UI state rather than backend routing to the normal workspace.

Dominant language
Rust
Stars
2.3k
Forks
236
Avg merge
2h 56m
Merged PRs (30d)
619

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GCWing/OpenBitFun

All issues in GCWing/OpenBitFun

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.