Task-created tab group appears in a different Yab window

Open
#1,009 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
desktop

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
  1. Open two normal Yab windows. Leave one window empty and keep a tab open in the other.
  2. Start a task from the empty window that will open several pages, such as “open example.com and example.org and compare their headings.”
  3. 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

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 yetanotherbrowser/yab

All issues in yetanotherbrowser/yab

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.