DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check running sessions from a browser over HTTPS with Think Term

Enable the browser listener and use an access token to reach your sessions from another device.

Credentials. A browser access token grants access to the server's terminal sessions, so treat it as a credential and do not share it.

Who it is forA developer away from their main machine who wants to glance at a running build or agent from a browser.

The problemWithout a way to reach the running session, checking progress means waiting until you return to the machine.

The outcomeYou open the Think Term web client in a browser and see the same server-held sessions.

What you need first

  • macOS, Linux, or Windows (the README lists these as desktop platforms)
  • Homebrew on macOS for the cask install, or Rust and platform build tools for a source build
  • Access to the machines you want to connect, if you use remote sessions
  • A second terminal window to run the TUI client

Steps

  1. Start Think Term and open Settings and then Web
  2. Enable the listener and create an access token for the browser
  3. Serve connections away from loopback over HTTPS, as the default requires
  4. Open the web client in a browser that supports WebGPU in a secure context
  5. Use the token to attach to the sessions and check progress

Prompt for your agent

Using the RoversX/ThinkTerm repo, enable the browser listener in Settings and then Web, create an access token, and open the web client from <device>. Expected output: the list of running sessions on the mux server. Verify that the browser shows the same sessions as the desktop app.

Caveat. The browser client requires WebGPU and a secure browser context, and browser access must be enabled explicitly, according to the README.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page