teamtrail 0.26.0-next.36 → 0.27.1-next.37

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
@@ -1,4 +1,4 @@
1
- <img src="https://raw.githubusercontent.com/teamtrailhq/teamtrail/main/brand/teamtrail-banner.gif?v=8" alt="Scout, the voice of Teamtrail, next to the name Teamtrail and a trail through the mountains." width="100%" />
1
+ <img src="https://raw.githubusercontent.com/teamtrailhq/teamtrail/main/brand/teamtrail-banner.gif?v=10" alt="The teamtrail wordmark, ending in an orange dot, above a dashed trail through the mountains that reaches the same orange destination." width="100%" />
2
2
 
3
3
  # teamtrail
4
4
 
@@ -27,8 +27,8 @@ The Lookout's address is always `http://127.0.0.1:<port>/`, never `localhost`, w
27
27
 
28
28
  ### Signing in
29
29
 
30
- The Lookout opens only in browsers you've paired. `teamtrail` opens the Lookout and prints a one-time **Sign in** link in its terminal; open it and click **Sign in this browser**. (The link is never passed to the browser on a command line, where other programs could read it.) A link works once, within 10 minutes, and only for the Lookout that printed it. A browser stays signed in while that Lookout runs, up to 30 days after it was last used; when you restart `teamtrail`, browsers and devices pair again (so a session a program grabbed while the Lookout was stopped opens nothing). Before the page sends its session, the server proves it is your Lookout; if it can't, the page says Teamtrail isn't running there and sends nothing. A browser that isn't paired sees "Pair this browser". For another browser on the same machine, run `teamtrail pair` in the repo while the Lookout runs: it prints a new link, after checking that the server at the Lookout's address really is that Lookout. To pair a phone or another computer (the Lookout started with `--host`), open Settings → You → Browsers & devices → **Pair a device** on the machine and type the short code on the device, or scan its QR code. Phones and other devices must pair again after every Lookout restart. The same page lists every paired browser with Revoke; a revoked browser is signed out at once.
31
- The session is never a cookie: browsers send cookies to every port of a host, so another server on your machine (an agent's dev server, say) would get it. It is kept in the Lookout page's own storage and sent by that page alone, and the code in a link travels after `#`, which no server sees. Sign-in stops a program on your machine, or a device on your network, that isn't a paired browser: an agent with `curl` can't approve its own work, answer its own questions or change your settings through the Lookout, and a device paired from Settings can read, answer and approve but never change what runs on the machine or whom it trusts. It can't stop a program that can read Teamtrail's config folder (it can make a pairing code, as `teamtrail pair` does) or your browser's profile on disk. The MCP endpoints keep their own tokens and are not affected.
30
+ The Lookout opens only in browsers you've paired. `teamtrail` opens your browser on the Lookout's sign-in page: click **Sign in this browser**. It also prints a one-time **Sign in** link in its terminal, for another browser. (A code is never passed to the browser on a command line, where other programs could read it. Teamtrail finds your default web browser by name, never whatever opens `.html` files, and opens it on a one-time page in Teamtrail's config folder, readable only by your user, that sends it on to a link with a code of its own. That code works once, for one minute, and the page is deleted once used, when the code expires, or when `teamtrail` stops. Anything that can read Teamtrail's config folder could read the code in that minute, so every sign-in through the opened page is printed in the terminal ("Signed in a browser (opened page)", with the time and a short id) and marked with that id in Settings → Browsers & devices: revoke one you didn't make. If your own tab then says the link was already used, someone else may have used it: check that list, or restart `teamtrail` to end every session. If no browser is found (a snap or Flatpak browser can't read the page), or the folder can't be written, the browser opens signed out and the terminal says why; use the printed link.) A link works once, within 10 minutes, and only for the Lookout that printed it. A browser stays signed in while that Lookout runs, up to 30 days after it was last used; when you restart `teamtrail`, browsers and devices pair again (so a session a program grabbed while the Lookout was stopped opens nothing). Before the page sends its session, the server proves it is your Lookout; if it can't, the page says Teamtrail isn't running there and sends nothing. A browser that isn't paired sees "Pair this browser". For another browser on the same machine, run `teamtrail pair` in the repo while the Lookout runs: after checking that the server at the Lookout's address really is that Lookout, it opens a browser tab ready to sign in the same way and prints the new link; `teamtrail pair --no-open` only prints it. To pair a phone or another computer (the Lookout started with `--host`), open Settings → You → Browsers & devices → **Pair a device** on the machine and type the short code on the device, or scan its QR code. Phones and other devices must pair again after every Lookout restart. The same page lists every paired browser with Revoke; a revoked browser is signed out at once.
31
+ The session is never a cookie: browsers send cookies to every port of a host, so another server on your machine (an agent's dev server, say) would get it. It is kept in the Lookout page's own storage and sent by that page alone, and the code in a link travels after `#`, which no server sees. Sign-in stops a program on your machine, or a device on your network, that isn't a paired browser: an agent with `curl` can't approve its own work, answer its own questions or change your settings through the Lookout, and a device paired from Settings can read, answer and approve but never change what runs on the machine or whom it trusts. It can't stop a program that can write Teamtrail's config folder (it can make a pairing code, as `teamtrail pair` does), one that can read it while a sign-in page Teamtrail opened waits (a minute at most; such a sign-in is announced), or one that can read your browser's profile on disk. The MCP endpoints keep their own tokens and are not affected.
32
32
 
33
33
  ## Connect your coding agent
34
34