Task-created tab group appears in a different Yab window
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
Research direction
Start by reading AgentTask.swift for the recorded origin window ID and Bench.swift for how task-owned tabs use the bound browser window. Reproduce the steps with two windows, especially starting the task from the empty one, then check whether the bound window matches the recorded origin. Done when the task's chat, tab group, and pages appear in the window where it started.
Written by the indexing model from the issue text.
Description
Yab version
Exact build unconfirmed.
Device
Mac, Apple silicon
macOS or iOS version
Unconfirmed.
Engine of the tab
Not about a page
Area
Agents
Steps to reproduce
- Open two normal Yab windows. Leave one window empty and keep a tab open in the other.
- Start a task from the empty window that will open several pages, such as “open example.com and example.org and compare their headings.”
- Open a tab in the window where the task started to reveal its chat. Check both sidebars for the task’s tab group.
What you expected
The task’s chat, tab group, and pages appear in the window where the task started.
What happened instead
The chat appeared in the window where the task started, but its tab group and pages appeared in the other window.
How often
Observed once. Frequency unconfirmed.
Additional context
AgentTask.swift records the originating window ID. Bench.swift creates task-owned tabs through its bound browser window. Check whether that browser window matches the recorded origin when the task starts without an active tab.
- Dominant language
- Swift
- Stars
- 648
- Forks
- 56
- Avg merge
- 21h 14m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yetanotherbrowser/yab
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yetanotherbrowser/yab#1008 ·
Maintainers usually reply within 2 days
-
area: passwords Broken bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yetanotherbrowser/yab#923 ·
Maintainers usually reply within 2 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#918 · 1 reaction ·
Maintainers usually reply within 2 days
-
iPhone: the + button and the checkmark sit on top of the Space switcher in the bottom barPossibly taken @ChaseRoofener claimed this 3 days ago. OpenAnnoying area: iphone bug needs info
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#915 · 3 comments ·
Maintainers usually reply within 2 days
-
CONTRIBUTING.md and CI run scripts/runs/tests_for.py, which is not in the repositoryPossibly taken @serafimcloud claimed this 3 days ago. OpenAnnoying in progress
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
yetanotherbrowser/yab#875 · 1 comment ·
Maintainers usually reply within 2 days
All issues in yetanotherbrowser/yab
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
swiftlang/swift-org-website#1608 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
haacked/switchboard#460 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
manaflow-ai/cmux#47572 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
borrowcheckmate/swimlie#48 ·
Maintainers usually reply within 1 day