webhelm 1.0.24 → 1.0.25

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -39,7 +39,7 @@ The daemon-managed Chrome Extension is installed from the npm Runtime and does n
39
39
 
40
40
  The compact popup shows daemon connectivity and per-workspace capacity and Session counts, with confirmation before stopping a Session or clearing Sessions in one workspace. The popup does not include a global stop-all action. These actions are executed by the same Node daemon as the CLI, over the existing CDP-backed Extension RPC. No shell access or HTTP listener is granted to the Extension. The persistent ChatGPT queue is not deleted, and queued work may create new Sessions afterward.
41
41
 
42
- New installations use the default Chrome tab group `WebHelm` and the idle page `helm.html`. Idle URLs use only `workspace` and `role=idle`; Lease URLs use Chrome's actual `tabId` for initial CDP target discovery. There is no separate slot identity. Every newly created WebHelm-managed tab group (default and custom) is placed at the far right of its Chrome window. Existing groups retain their user-chosen position during restoration, legacy migration and Session allocation. Chrome-saved tab group shortcuts in the bookmarks bar are separate from active groups and cannot safely be deduplicated through the Extension API. Legacy `Harness` default groups migrate only when their tabs are idle. Custom workspace names are unchanged; the old `workspace.html` path and lease titles remain readable until their Sessions finish. Closing an allocated Session returns its managed tabs to the idle page, retaining physical Chrome targets, while unleased popup children are closed. Do not manually remove active managed tabs.
42
+ New installations use the default Chrome tab group `WebHelm` and the idle page `helm.html`. Idle URLs use only `workspace` and `role=idle`; Lease URLs use Chrome's actual `tabId` for initial CDP target discovery. There is no separate slot identity. Every newly created WebHelm-managed tab group (default and custom) is placed at the far left of its Chrome window, immediately after pinned tabs. Existing groups retain their user-chosen position during restoration, legacy migration and Session allocation. Chrome-saved tab group shortcuts in the bookmarks bar are separate from active groups and cannot safely be deduplicated through the Extension API. Legacy `Harness` default groups migrate only when their tabs are idle. Custom workspace names are unchanged; the old `workspace.html` path and lease titles remain readable until their Sessions finish. Closing an allocated Session returns its managed tabs to the idle page, retaining physical Chrome targets, while unleased popup children are closed. Do not manually remove active managed tabs.
43
43
 
44
44
  For a real browser integration check on macOS, run `node test/e2e/extension-control.e2e.mjs`; it creates a temporary isolated Chrome profile and daemon and does not touch the current production Sessions.
45
45
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "webhelm",
3
- "version": "1.0.24",
3
+ "version": "1.0.25",
4
4
  "description": "Agent browser automation in a visible managed Chrome with persistent JavaScript sessions",
5
5
  "type": "module",
6
6
  "bin": {
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "manifest_version": 3,
3
3
  "name": "WebHelm",
4
- "version": "0.4.9",
4
+ "version": "0.4.10",
5
5
  "description": "Own named Chrome tab-group workspaces and lazy reusable tab pools for browser agents.",
6
6
  "permissions": [
7
7
  "storage",
@@ -242,10 +242,14 @@ export class WorkspaceManager {
242
242
  return await this.chrome.tabs.query({ groupId });
243
243
  }
244
244
 
245
- // New groups belong at the right edge, regardless of Chrome's new-tab
246
- // insertion policy. Never reorder existing groups on restore or lease.
247
- async positionNewGroupRightmost(groupId) {
248
- await this.chrome.tabGroups.move(groupId, { index: -1 });
245
+ // New groups belong immediately after pinned tabs, regardless of Chrome's
246
+ // insertion policy. Existing groups keep their order on restore and lease.
247
+ async positionNewGroupLeftmost(groupId) {
248
+ const groupTabs = await this.groupTabs(groupId);
249
+ if (!groupTabs.length) return;
250
+ const windowTabs = await this.chrome.tabs.query({ windowId: groupTabs[0].windowId });
251
+ const firstUnpinned = windowTabs.filter(tab => tab.pinned).length;
252
+ await this.chrome.tabGroups.move(groupId, { index: firstUnpinned });
249
253
  }
250
254
 
251
255
  tabUrl(tab) {
@@ -497,7 +501,7 @@ export class WorkspaceManager {
497
501
  for (const tab of created) this.markOwned(tab.id);
498
502
  const groupId = await this.chrome.tabs.group({ tabIds: created.map((tab) => tab.id) });
499
503
  await this.chrome.tabGroups.update(groupId, { title: name, collapsed: true });
500
- await this.positionNewGroupRightmost(groupId);
504
+ await this.positionNewGroupLeftmost(groupId);
501
505
  for (const tab of created) await this.waitForIdleTab(tab.id, name);
502
506
  return await this.status(name);
503
507
  }