Original Summary

A month ago I shared Browser Control, a Chromium side-panel extension that lets Codex work with the tabs and webpages already open in Chrome or Brave. The most useful response was that supervision made the idea feel less scary, so I kept that as the center of the product. The new open-source build adds taught skills. A user records a real browser workflow, reviews the captured steps, and saves it locally. Later, Codex can load the matching procedure and repeat it through the same restricted browser tools. A saved skill does not grant extra permissions or bypass the Stop control, action budget, short-lived element references, or safety refusals. I also expanded the native companion beyond macOS. Windows installation and Chrome/Brave native-host registration have been tested. Linux installation support is implemented, although broader real-desktop testing is still pending and sandboxed Snap/Flatpak browsers are not supported. One honest release detail: GitHub main is on 0.3.4, while the public Chrome Web Store still serves 0.3.2. The newest work is available from source while I prepare the Store update. GitHub: https://github.com/07rjain/browser-control Chrome Web Store: https://chromewebstore.google.com/detail/browser-control/mpdfhhhjgbpdpfnkjbnboebdjokfjglf I built this project. I’m looking for feedback on two things: which repetitive browser workflow would you teach first, and what would you need to see before trusting a recorded skill?   submitted by   /u/pleasetellme-1 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/10 14:29:57