daily-focus 1.1.1-dev.3 → 1.2.0-dev.11

package/README.md

@@ -35,9 +35,11 @@ To use your own data:
 npx daily-focus
 ```
 
-Until the first brief exists, the Today tab walks you through the rest: what it
-briefs, your objective, which coding-agent CLI writes the brief (Claude Code or
-Codex), and where it should look. Everything stays on the settings page afterwards.
+A new store opens on the setup screen: a few questions, one at a time, each with
+the likely answer already ticked. Once you've chosen the coding-agent CLI that writes
+the brief (Claude Code or Codex), it looks into the rest for you, such as which of
+your calendars are work ones, so most answers are a click. Everything stays on the
+settings page afterwards.
 To keep it running in the background on macOS, install it and run it as a service:
 
 ```sh
@@ -64,13 +66,6 @@ since you completed something that advanced your objective.
 - Mark tasks **Done** when you've handled them.
 - **Snooze** an item until a date, or **Dismiss** it if it doesn't need attention.
 - Leave a **Note** for the next brief, such as "already replied on Slack".
-- Press **f** for focus mode, which shows your top item and agenda.
-- Press **p** on an item to start a focus timer. Its countdown appears in the tab
-  title, and the session becomes part of the next brief's context.
-
-The timer keeps counting after its target time. On macOS, it ends a session when
-you've been away from the machine, excluding the time you were away. On systems
-without idle detection, a two-hour limit caps the recorded session.
 
 You can undo item actions except notes. The page updates as new data arrives, and
 the theme button switches between system, light, and dark mode.
@@ -90,8 +85,10 @@ The second tab shows your open pull requests in seven buckets:
 | Drafts | Pull requests you haven't marked ready for review. |
 
 Park a pull request until a date, leave a note, or click **Nudged** after asking
-for a review. Nudged records a note; it doesn't send a message. Completing a task
-about a pull request in the brief doesn't remove that pull request from the board.
+for a review. Nudged records that you asked; it doesn't send a message. The pull
+request moves to a Nudged section for a day, then goes back to Waiting on reviewers
+with "time to ask" if nobody has reviewed it. Completing a task about a pull
+request in the brief doesn't remove that pull request from the board.
 
 Cancelled checks appear as "cancelled, no verdict" rather than failures.
 When a check is rerun, the board uses its newest workflow run or attempt.
@@ -111,6 +108,14 @@ Draft pull requests count as open. Closed pull requests don't prove that a ticke
 is finished, so the board leaves that decision to you. Park a reminder or leave a
 note when there's more work planned.
 
+Jira can take days to hear that a pull request merged, so the board also checks
+GitHub. It searches your open pull requests and the ones closed in the last 60
+days, and matches them to tickets by the key in the title, branch, description
+or commit messages. An open pull request on GitHub always counts. GitHub can
+also mark a ticket's pull requests as all closed, but only when it found at least
+as many as Jira has linked. A row that GitHub changed lists those pull requests
+under **GitHub, ahead of Jira**.
+
 Switch to **Working on** to see your in-progress tickets grouped by status,
 including ones that also need a status check. You can narrow this view in
 [SETUP.md](SETUP.md#jira).
@@ -127,15 +132,28 @@ why is CI red, what does this thread actually want from me. With
 `DAILY_FOCUS_ASSISTANT` set to `claude` or `codex`, every item's panel gets an
 assistant that runs that CLI headless against the item, with quick actions for the
 common asks and a field for anything else. Click a card to open its panel, where its
-notes live too; the reply streams in there, and you can follow up in the same
-conversation. The panel stays on the item it was opened for while you move through
-the list.
-
-It reads and drafts, and that is all. An email reply is created as a Gmail draft on
-the thread, so it is waiting there when you open the mail; a reply to a reviewer is
-handed back as text for you to post. It never sends, posts, or edits a file, and it
-has no checkout: fixing conflicts or a build is work for a real coding session, and
-this is for the questions you would otherwise answer by opening six tabs.
+notes live too. While the assistant works, the panel shows what it is doing: each
+command it runs and each page, thread or ticket it reads, with a clock, and a cross
+on anything that failed, such as a repository it couldn't see. Once it answers,
+that trail folds away under the answer. The answer has buttons to copy it, or any
+block in it meant for pasting, and to open a draft it created. The field stays at
+the foot of the panel, so you can follow up in the same conversation. The panel
+stays on the item it was opened for while you move through the list.
+
+It can also answer before you ask. With **Answer ahead** on in the settings, when a
+pull request starts waiting on you because someone reviewed it or a check failed,
+the assistant assesses the review or explains the failure on its own. The first
+line of its answer appears on the row, such as "Flaky, not yours: the Safari job
+timed out", so the card already says what to do. It asks about each state once,
+one at a time, and no more than ten times a day unless you change the limit.
+
+It is told to read and draft, and nothing more. An email reply is created as a Gmail
+draft on the thread, so it is waiting there when you open the mail; a reply to a
+reviewer is handed back as text for you to post. It is told never to send, post, or
+edit a file, and it has no checkout: fixing conflicts or a build is work for a real
+coding session, and this is for the questions you would otherwise answer by opening
+six tabs. How much of that the CLI itself enforces differs between Claude Code and
+Codex; see [What the assistant can do](SETUP.md#what-the-assistant-can-do).
 
 ## The morning agent
 
@@ -165,8 +183,6 @@ Press **?** in the dashboard to see the shortcuts.
 | `a` | Open the panel, ready to ask the assistant |
 | `o` | Open the source link |
 | `u` | Undo the last action |
-| `f` | Toggle focus mode |
-| `p` | Start / stop a focus session |
 | `r` | Refresh the current board |
 | `w` | Switch Jira views |
 | `,` | Settings |

package/SETUP.md

@@ -27,18 +27,56 @@ and `npm start` runs it in the terminal. Each `daily-focus <command>` below is
 `npm run <command>` in a checkout, with two differences: `build-calendar` is
 `build:calendar`, and flags go after `--`, as in `npm run audit -- --against <file>`.
 
-Until the first brief exists, the Today tab walks you through setting it up:
-
-1. **What it briefs**: your work, or your personal life. See
+A new store opens on the setup screen. It first looks for Codex and Claude Code:
+on your login shell's PATH, then where their installers put them, and checks that
+the one it finds is logged in. With one ready it doesn't ask: it uses Codex if
+that is ready, otherwise Claude Code, and says so in a line you can **Change**.
+With neither ready, it says what is wrong with each and the command that fixes it
+(`codex login`, `claude auth login`), links to the installers, and takes the path
+to one it couldn't find.
+
+Then it asks a few questions, one at a time, and each comes with the answer you
+most likely want already ticked: confirm it or change it. A list can be left
+unticked and a field empty. Two questions can be left, by a button that says what
+that does: **Decide later** for the agent, and **Leave this out** for who you are.
+**Change** reopens an earlier answer.
+
+1. **Who writes the brief**, only when it couldn't pick for you.
+2. **What it briefs**: your work, or your personal life. See
    [A personal instance](#a-personal-instance) for running both.
-2. **Your objective**: the one thing you're trying to achieve, which the agent
-   ranks the day against.
-3. **Who writes the brief**: Claude Code or Codex, whichever it finds installed.
-4. **Where it should look**: your source list, which starts from a template with
-   what `gh` and `git` know about you filled in.
-5. **What else to show**: the pull request board, the Jira board and the live
-   agenda, each with its status and a button to turn it off.
-6. **Write my first brief**, which runs the agent once while you watch.
+3. **When it runs**, and on which days.
+4. **Who you are**: your name as meeting notes write it, your email, and each
+   GitHub account `gh` is logged in to, with what it's for.
+5. **What else to show**: the pull request board and the Jira board, each with
+   its status.
+6. **Which calendars** the brief reads, which the live agenda follows too.
+7. **Your objective**, which the agent ranks the day against, and what's in the
+   way. It suggests a few from what you've been doing, when something stands
+   out, and writes one up from whatever you tell it, however rough.
+
+The [assistant](#ask-the-assistant) isn't asked about: it comes on with the CLI
+that writes the brief, unless you've set it already.
+
+Once you've said what it briefs, the CLI looks into the others in the background,
+one short session each, so the slow ones are ready when you get to them. It reads
+`gh`, your mail and your calendars to tell work from personal, and says in a
+sentence why it ticked what it did. Reply under that sentence with what to change,
+such as "also the on-call rota", and it tries again, answering in the same place.
+Continue before it has finished and it asks first, then stops and keeps what the
+card holds.
+
+The sessions run on the newest flagship model at low effort (Opus for Claude Code,
+the first model in Codex's own list for Codex), which measured as fast as the
+lighter models and, unlike them, told your calendars from other people's. They
+only read, in an empty directory. Claude Code is given read tools by name, and
+under Codex every connector write is refused, drafts included; `gh` and `acli` are
+held to reading by their instructions, as
+[the assistant's](#what-the-assistant-can-do) are.
+
+Nothing is saved until the last step, **Write my first brief**. It saves the
+settings, writes your source list from the answers (unless you already have one,
+which it leaves alone) and your objective, restarts the dashboard to apply them,
+and runs the agent once while you watch.
 
 Everything in it stays on the settings page afterwards: the gear in the header, or
 <kbd>,</kbd>. The dashboard keeps its files in `~/.daily-focus/`, and links the
@@ -52,6 +90,8 @@ terminal open while you use the dashboard. `daily-focus --help` lists the rest.
 
 If you'd rather write the files by hand, `daily-focus init` creates the store with
 templates for both. It preserves existing files, so you can safely run it again.
+A setting given in the environment, such as `DAILY_FOCUS_PROFILE`, is shown on the
+setup screen as answered and isn't asked.
 
 ## Set your objective and sources
 
@@ -91,7 +131,7 @@ Keep real names, account handles, and work details in this private store, outsid
 
 The dashboard runs the agent through a coding-agent CLI you already have. Install
 and log in to the [Codex CLI](https://developers.openai.com/codex/cli) or
-[Claude Code](https://code.claude.com/docs), and choose it in the setup steps or
+[Claude Code](https://code.claude.com/docs), and choose it on the setup screen or
 under **Morning agent** in the settings. In `.env` or the environment that is:
 
 ```dotenv
@@ -108,7 +148,8 @@ half minute. The days are Monday to Friday unless `DAILY_FOCUS_AGENT_DAYS` says
 otherwise; see [Match your working week](#match-your-working-week).
 `DAILY_FOCUS_AGENT_AT=off` means the dashboard never starts a run on its own; the
 refresh icon still does. A new store's first brief always comes from the setup
-steps' button, so the clock never runs the agent before you've told it where to look.
+screen's last button, so the clock never runs the agent before you've told it where
+to look.
 
 "Your time" is the time zone of the browser you last looked at the dashboard
 in. The page tells the dashboard when it loads, reconnects or comes back into view,
@@ -126,21 +167,30 @@ it finishes, and a chat where you can ask it why it did what it did. See
 The agent reaches your sources the way the CLI does:
 
 - **Codex** runs in its workspace-write sandbox with network access, confined to the
-  store. Connectors from the Codex app are found through its plugin catalogue. There
-  is nobody to approve a command outside the sandbox, so the agent reports that
-  restriction for any `gh` command that needs it, such as switching accounts.
+  store. Connectors from the Codex app are found through its plugin catalogue, and
+  every write through one is refused: a connector tool counts as a write unless it
+  is marked read-only. A command that needs to leave the sandbox, such as `gh`
+  switching accounts, is decided by your own Codex approval settings, as it would be
+  in your Codex. With nobody set to approve, the agent reports that restriction; with
+  Codex's automatic reviewer, the reviewer decides. The dashboard won't start a run
+  on a Codex older than 0.144.0, which would ignore the refusal of connector writes;
+  update Codex if a run fails saying so.
 - **Claude Code** may write `items.json` and nothing else in the store, and reach
   its sources with only what `DAILY_FOCUS_AGENT_TOOLS` allows. The default covers
   GitHub, Jira, web pages and the claude.ai Gmail connector. Add your calendar, chat
   and document connectors to the list by name, or the brief will report them as
-  unreachable.
+  unreachable. The default allows every Gmail tool, sending included, and `gh` and
+  `acli` can write as well as read; the agent's instructions forbid changing
+  anything. To narrow Gmail to reading, name its tools instead of the connector, as
+  [What the assistant can do](#what-the-assistant-can-do) shows, without the two
+  draft tools.
 
 Set `DAILY_FOCUS_AGENT_MODEL` and `DAILY_FOCUS_AGENT_EFFORT` if the CLI's own
 defaults are not what you want for a brief; a brief is worth a high effort. If the
 server can't find the CLI, set `DAILY_FOCUS_AGENT_BIN`.
 
-The agent writes `items.json`. The dashboard records your actions and focus sessions
-for the next run to read.
+The agent writes `items.json`. The dashboard records your actions for the next run
+to read.
 
 After the first run, read its report (click "updated … ago"): it says which sources
 it couldn't reach. To check the brief against the payload contract, run:
@@ -228,6 +278,11 @@ Clicking a status in the dashboard writes one transition to Jira. All other Jira
 access is read-only. See the [ticket board guide](README.md#the-jira-ticket-board)
 for workflow limits and undo behavior.
 
+The board also asks GitHub about your pull requests, because Jira can learn of
+them days late. It uses the pull request board's accounts and scope, and nothing
+else needs to be configured. With `DAILY_FOCUS_GITHUB=off`, the ticket board uses
+Jira alone.
+
 Set `DAILY_FOCUS_JIRA=off` to disable the board.
 
 ### Live calendar on macOS
@@ -277,14 +332,72 @@ the CLI is configured with; `DAILY_FOCUS_ASSISTANT_MODEL` and
 `DAILY_FOCUS_ASSISTANT_EFFORT` override them. If the server can't find the CLI,
 set `DAILY_FOCUS_ASSISTANT_BIN` to its path.
 
-The assistant reads and drafts; it never sends, posts or edits anything, and it has
-no checkout to work in. That is deliberate. Fixing merge conflicts or a failing build
-belongs in a real coding session; this panel is for the questions you'd otherwise
-answer by opening six tabs. The Gmail draft is the one thing it creates, through the
-Gmail tool the CLI has: with Claude Code that is the claude.ai Gmail connector, which
-`DAILY_FOCUS_ASSISTANT_TOOLS` allows by default; with Codex it is the Gmail plugin
-from the Codex app, which the CLI finds through its plugin catalogue. Without either,
-the assistant hands you the text instead and says so.
+The assistant is told to read and draft, and never to send, post or edit anything,
+and it has no checkout to work in. That is deliberate. Fixing merge conflicts or a
+failing build belongs in a real coding session; this panel is for the questions you'd
+otherwise answer by opening six tabs. The Gmail draft is the one thing it creates,
+and revises when you ask, through the Gmail tool the CLI has: with Claude Code that
+is the claude.ai Gmail connector, which `DAILY_FOCUS_ASSISTANT_TOOLS` allows by
+default; with Codex it is the Gmail app linked to your ChatGPT account, which the CLI
+finds through its plugin catalogue. Without either, the assistant hands you the text
+instead and says so.
+
+### What the assistant can do
+
+The assistant runs the CLI you already use, with the access that CLI already has.
+The dashboard narrows some of that, and leaves the rest to the assistant's
+instructions. What the CLI itself enforces:
+
+- **Claude Code** may use only the tools in `DAILY_FOCUS_ASSISTANT_TOOLS`, and never
+  its file-editing tools, whatever the list says; anything else is refused rather
+  than asked about. Rules in your own Claude Code settings that allow a tool still
+  apply. The default list is broader than the assistant needs:
+  `mcp__claude_ai_Gmail` allows every tool on the Gmail connector, sending and
+  deleting included, and `gh` and `acli` can comment, merge and move tickets as well
+  as read. Only the instructions keep it from doing those. To hold it to reading
+  mail and drafting replies, name the Gmail tools instead of the connector:
+
+  ```dotenv
+  DAILY_FOCUS_ASSISTANT_TOOLS=Bash(gh *),Bash(acli *),WebFetch,mcp__claude_ai_Gmail__search_threads,mcp__claude_ai_Gmail__get_thread,mcp__claude_ai_Gmail__get_message,mcp__claude_ai_Gmail__list_labels,mcp__claude_ai_Gmail__list_drafts,mcp__claude_ai_Gmail__get_draft,mcp__claude_ai_Gmail__create_draft,mcp__claude_ai_Gmail__update_draft
+  ```
+
+  A tool left off the list is refused, so if the connector renames one, the
+  assistant reports that it can't reach your mail rather than working around it.
+- **Codex** refuses every write through a connector (Gmail, Calendar, Drive, GitHub
+  and the other apps your ChatGPT account links) except creating and revising a
+  Gmail draft. A connector tool counts as a write unless it is marked read-only. A
+  tool you have told Codex to always allow, or an app given approval settings of its
+  own in your Codex config, keeps them. Computer use, the plugins that act in your
+  apps and browser with your sign-ins, is off unless you turn on
+  `DAILY_FOCUS_ASSISTANT_COMPUTER_USE`; the dashboard checks with Codex that it is
+  off before each session, and refuses to start one it can't confirm. Shell
+  commands follow your own Codex config: the sandbox keeps writes in the
+  assistant's working directory, and a command that needs to leave it is decided
+  by your Codex approval settings, as it would be in your own Codex. That keeps
+  `gh` working, and means it can write. All of this needs Codex 0.149.0 or
+  newer, and the page warns when yours is older. Before 0.144.0 Codex silently
+  ignores the refusal of connector writes, so the dashboard won't start the
+  assistant or the morning agent on it at all; before 0.149.0 it can't switch
+  computer use off, so the assistant won't answer while that setting is off.
+
+### Answer ahead
+
+With `DAILY_FOCUS_ASSISTANT_AUTO=on`, the dashboard asks the assistant before you
+do. When a pull request lands in *Waiting on you* because someone reviewed or
+commented, it asks the assistant to assess the review. When a check fails, it asks
+for an explanation of the failure. The first line of the answer appears on the row,
+on the board and on the brief item for the same pull request, while it still
+matches the pull request's state. The whole answer is in the panel, as a turn you
+can follow up on.
+
+It asks about each state once. A new comment or a new failure is a new question;
+the same checks failing again on the same commit are not. It runs one question at a
+time and never on a row you're asking about, and it starts no more than
+`DAILY_FOCUS_ASSISTANT_AUTO_LIMIT` a day (10 by default). It uses only those two
+quick actions, which read and answer, and never one that drafts. It follows the
+board, which reads only while a tab is open, so it asks while you have the
+dashboard open. It is off by default because it spends the CLI's usage without
+you pressing anything.
 
 Its instructions live in `prompts/assistant.md`, linked into the store as
 `assistant.md` each time the dashboard starts. What it says stays in the chat in the panel: it
@@ -398,8 +511,8 @@ daily-focus service --remove
 
 Daily Focus can brief your personal life as well as your work: email, family
 calendars, Apple Reminders, Apple Messages, e-Boks and your own GitHub projects. Run it as a second instance
-with its own store, server and morning agent, and choose **Personal life** in its
-setup steps, or set:
+with its own store, server and morning agent, and choose **Personal life** on its
+setup screen, or set:
 
 ```dotenv
 DAILY_FOCUS_PROFILE=personal
@@ -408,7 +521,7 @@ DAILY_FOCUS_PROFILE=personal
 The dashboard then links the personal prompt, `prompts/morning-brief-personal.md`,
 into the store as `prompt.md`, and the source list starts from a template with
 sections for those sources. The profile also switches off
-the Jira board and away detection, and gives the tab a green house icon instead of the blue briefcase. The pull request
+the Jira board, and gives the tab a green house icon instead of the blue briefcase. The pull request
 board stays on for side projects; point it at your personal account with
 `DAILY_FOCUS_GITHUB_ACCOUNTS`, or set `DAILY_FOCUS_GITHUB=off`.
 
@@ -469,9 +582,7 @@ matters when `DAILY_FOCUS_FREE_WINDOWS` is off.
 | `DAILY_FOCUS_MIN_FREE_WINDOW` | `45` | Minutes before a gap counts as a focus window |
 | `DAILY_FOCUS_STALE_AFTER_HOURS` | `24` | When to expect a refresh. Shows an informational message for 45 minutes before warning that the agent may not have run. Counted only in hours a run was due, so days off never trip it |
 | `DAILY_FOCUS_AGENT_DAYS` | `1-5` | Weekdays the dashboard runs the agent on, cron-style and cron-numbered: `1-5` for Monday to Friday, `0-4` for Sunday to Thursday, `0,6` for a weekend-only run |
-| `DAILY_FOCUS_SESSION_MINUTES` | `25` | Default focus session length |
-| `DAILY_FOCUS_AWAY_AFTER` | `10`; `0` for personal | Minutes of an untouched machine before a session is closed at the last sign of life. `0` turns it off |
-| `DAILY_FOCUS_GITHUB` | `on` | `off` disables the pull request board; nothing is polled |
+| `DAILY_FOCUS_GITHUB` | `on` | `off` disables the pull request board, and the ticket board stops checking GitHub; nothing is polled |
 | `DAILY_FOCUS_GITHUB_ACCOUNTS` | *gh's active account* | Logins to poll as, comma-separated, each resolved with `gh auth token --user` |
 | `DAILY_FOCUS_GITHUB_SCOPE` | *everything* | Organisations or `owner/repo` entries to limit the board to, comma-separated |
 | `DAILY_FOCUS_GITHUB_MERGE_GATE_CHECKS` | *none* | Check names that stand for a repository's whole merge policy, comma-separated and matched exactly. Their rows get the *Waiting on merge gate* bucket |
@@ -493,13 +604,16 @@ matters when `DAILY_FOCUS_FREE_WINDOWS` is off.
 | `DAILY_FOCUS_ASSISTANT_BIN` | *the CLI's name* | Path to the assistant's CLI, for when the server's PATH lacks it. `~` is expanded |
 | `DAILY_FOCUS_ASSISTANT_MODEL` | *the CLI's own* | Model passed to the CLI untouched: an alias like `opus`, or a full id. Unset passes no flag |
 | `DAILY_FOCUS_ASSISTANT_EFFORT` | *the CLI's own* | Effort passed to the CLI untouched: `low`, `medium`, `high`, `xhigh` or `max`. Unset passes no flag |
-| `DAILY_FOCUS_ASSISTANT_TOOLS` | `Bash(gh *),Bash(acli *),WebFetch,mcp__claude_ai_Gmail` | What Claude Code may use without asking, in its permission syntax, comma-separated. Editing tools are denied regardless. Ignored by Codex |
+| `DAILY_FOCUS_ASSISTANT_TOOLS` | `Bash(gh *),Bash(acli *),WebFetch,mcp__claude_ai_Gmail` | What Claude Code may use without asking, in its permission syntax, comma-separated. Editing tools are denied regardless. The default allows every Gmail tool, sending included; see [What the assistant can do](#what-the-assistant-can-do) to narrow it. Ignored by Codex |
+| `DAILY_FOCUS_ASSISTANT_COMPUTER_USE` | `off` | `on` lets the assistant use Codex's computer-use and browser plugins, which act in your apps and browser with your sign-ins. `off` switches them off for its runs. Ignored by Claude Code, which uses only the tools in its list |
+| `DAILY_FOCUS_ASSISTANT_AUTO` | `off` | `on` asks the assistant ahead about pull requests waiting on you, after a review or a failing check, and puts the answer's first line on the row. See [Answer ahead](#answer-ahead) |
+| `DAILY_FOCUS_ASSISTANT_AUTO_LIMIT` | `10` | How many times a day the assistant may start on its own, from 1 to 100 |
 | `DAILY_FOCUS_AGENT` | `off` | `codex` or `claude` lets the dashboard run the morning agent through that CLI: each scheduled morning, and from the refresh icon beside the brief's age. `off` hides it |
 | `DAILY_FOCUS_AGENT_AT` | `07:00` | Local time, `HH:MM`, at which the dashboard starts the agent on each scheduled day, or as soon as it is running after that. `off` means it never starts one on its own; the refresh icon still does. Needs `DAILY_FOCUS_AGENT` |
 | `DAILY_FOCUS_AGENT_BIN` | *the CLI's name* | Path to that CLI, for when the server's PATH lacks it. `~` is expanded |
 | `DAILY_FOCUS_AGENT_MODEL` | *the CLI's own* | Model passed to the CLI untouched. Unset passes no flag |
 | `DAILY_FOCUS_AGENT_EFFORT` | *the CLI's own* | Effort passed to the CLI untouched. Unset passes no flag |
-| `DAILY_FOCUS_AGENT_TOOLS` | `Bash(gh *),Bash(acli *),WebFetch,mcp__claude_ai_Gmail` | What Claude Code may use to reach your sources, in its permission syntax, comma-separated. Writing `items.json`, and nothing else in the store, is allowed regardless. Ignored by Codex |
+| `DAILY_FOCUS_AGENT_TOOLS` | `Bash(gh *),Bash(acli *),WebFetch,mcp__claude_ai_Gmail` | What Claude Code may use to reach your sources, in its permission syntax, comma-separated. Writing `items.json`, and nothing else in the store, is allowed regardless. The default allows every Gmail tool, sending included. Ignored by Codex |
 
 ## If something looks wrong
 
@@ -507,9 +621,10 @@ matters when `DAILY_FOCUS_FREE_WINDOWS` is off.
   which it ends with. Run `daily-focus service` to keep it running. If the
   service is installed and the page still doesn't load, read
   `~/Library/Logs/local.daily-focus.log`.
-- Before the first brief, the Today tab shows the setup steps. Once a brief has
-  existed, an empty Today tab means the agent hasn't written a new `items.json`:
-  start a run from the refresh icon beside the brief's age.
+- After setup and before the first brief, the Today tab says where the first brief
+  is, and offers to run it again if it didn't finish. Once a brief has existed, an
+  empty Today tab means the agent hasn't written a new `items.json`: start a run
+  from the refresh icon beside the brief's age.
 - A stale brief needs an agent run. Refreshing a board doesn't regenerate the brief;
   the icon beside the brief's age does. Click "updated … ago" to see what the last
   run said, or whether there was one: the dashboard has to be running at

package/dist/{audit-B5GKGH2P.js → audit-F26VGPOO.js}

@@ -1,7 +1,7 @@
 import {
   readSystemZone,
   startingZone
-} from "./chunk-AUBJ2IDQ.js";
+} from "./chunk-GVLNDQVQ.js";
 import {
   linkState
 } from "./chunk-QKT2FAB5.js";
@@ -11,8 +11,9 @@ import {
   parseBrief,
   readArchiveIndex,
   resolveItems,
-  runContractChecks
-} from "./chunk-C6FXWHGT.js";
+  runContractChecks,
+  setsStatus
+} from "./chunk-CPJ6LOVC.js";
 import {
   BRIEF_REFRESH_GRACE_HOURS,
   describeSchedule,
@@ -22,7 +23,7 @@ import {
   resolveSchedule,
   runsOn,
   workingMsBetween
-} from "./chunk-NWYOCDUU.js";
+} from "./chunk-4DZEBUPU.js";
 import {
   command
 } from "./chunk-BC2W7NND.js";
@@ -180,7 +181,7 @@ if (!previous) {
   const reproduced = [...previousIds].filter((id) => currentIds.has(id));
   const dropped = [...previousIds].filter((id) => !currentIds.has(id));
   const added = [...currentIds].filter((id) => !previousIds.has(id));
-  const actedOn = new Set(actions.filter((a) => a.action !== "note").map((a) => a.id));
+  const actedOn = new Set(actions.filter(setsStatus).map((a) => a.id));
   const addedFingerprints = new Map(added.map((id) => [fingerprintId(id), id]));
   const handled = dropped.filter((id) => actedOn.has(id));
   const drifted = dropped.filter((id) => !actedOn.has(id) && addedFingerprints.has(fingerprintId(id)));

package/dist/{chunk-NWYOCDUU.js → chunk-4DZEBUPU.js}

@@ -353,7 +353,10 @@ function envAssistant(env) {
     binPath: expandHome((env.DAILY_FOCUS_ASSISTANT_BIN ?? "").trim() || (agent ?? "claude")),
     model: envString("DAILY_FOCUS_ASSISTANT_MODEL", "", env) || null,
     effort: envString("DAILY_FOCUS_ASSISTANT_EFFORT", "", env) || null,
-    tools: tools.length > 0 ? tools : DEFAULT_ASSISTANT_TOOLS
+    tools: tools.length > 0 ? tools : DEFAULT_ASSISTANT_TOOLS,
+    computerUse: envFlag("DAILY_FOCUS_ASSISTANT_COMPUTER_USE", false, env),
+    auto: envFlag("DAILY_FOCUS_ASSISTANT_AUTO", false, env),
+    autoLimit: envBounded("DAILY_FOCUS_ASSISTANT_AUTO_LIMIT", 10, 1, 100, env)
   };
 }
 var DEFAULT_ASSISTANT_TOOLS = ["Bash(gh *)", "Bash(acli *)", "WebFetch", "mcp__claude_ai_Gmail"];
@@ -439,15 +442,10 @@ function loadConfig(env = loadEnv()) {
     schemaFile: resolve2(dataDir, "items.schema.json"),
     schemaSource: resolve2(import.meta.dirname, "..", "schema", "items.schema.json"),
     archiveDir: resolve2(dataDir, "archive"),
-    sessionFile: resolve2(dataDir, "session.json"),
-    sessionsLogFile: resolve2(dataDir, "sessions.jsonl"),
     pullsFile: resolve2(dataDir, "prs.json"),
     calendarFile: resolve2(dataDir, "calendar.json"),
     ticketsFile: resolve2(dataDir, "tickets.json"),
     timeZoneFile: resolve2(dataDir, "timezone.json"),
-    // The same 1 to 120 the session endpoint holds a start to.
-    sessionMinutes: envBounded("DAILY_FOCUS_SESSION_MINUTES", 25, 1, 120, env),
-    awayAfterMinutes: envBounded("DAILY_FOCUS_AWAY_AFTER", profile === "personal" ? 0 : 10, 0, 24 * 60, env),
     port: envBounded("DAILY_FOCUS_PORT", 4321, 0, 65535, env),
     host: envString("DAILY_FOCUS_HOST", "127.0.0.1", env),
     freeWindows: envFlag("DAILY_FOCUS_FREE_WINDOWS", profile !== "personal", env),
@@ -464,12 +462,16 @@ function loadConfig(env = loadEnv()) {
     assistantPromptFile: resolve2(dataDir, "assistant.md"),
     assistantPromptSource: resolve2(import.meta.dirname, "..", "prompts", "assistant.md"),
     agent: envAgent(env),
-    agentLogFile: resolve2(dataDir, "agent.jsonl")
+    agentLogFile: resolve2(dataDir, "agent.jsonl"),
+    onboardingFile: resolve2(dataDir, "onboarding.json"),
+    onboardingDir: resolve2(dataDir, "onboarding"),
+    onboardingPromptSource: resolve2(import.meta.dirname, "..", "prompts", "onboarding.md")
   };
 }
 
 export {
   LAUNCH_SETTINGS,
+  expandHome,
   readDotEnv,
   envSources,
   layerEnv,