devpit

Assistant mode

Schedules, routines and a heartbeat that let an orchestrator speak first, to tell you what needs you, never to start work.

Last updated

An orchestrator acts when you write to it. Its Schedules, and Assistant mode, let it speak first: to tell you something at a time you chose, or when something new needs you. Neither starts work.

Schedules

Schedules, in the orchestrator's sidebar, is one list of every time it knows about: the reminders on cards with a date, in the orchestrator and its linked projects, and the routines you set. Each row says when it goes off — day, time and zone — what it is about, its project and card, whether it repeats, whether it is waiting, went off, done or paused, and when it last ran.

  • A routine has Pause / Resume and Edit.
  • A reminder has Edit, to move its time, Resolve and Delete.
  • New reminder and New routine make one by hand.

Asked to schedule something, the orchestrator proposes it. The proposal waits on top of Schedules with Add and Drop, and nothing is scheduled until you click.

Routines

A routine runs at its time on the days you choose, unless it is paused, and then waits for its next time.

Routine What it tells you
Morning summary the briefing below
CI failures the open pull requests whose checks fail
Pull requests waiting the open pull requests
Cards waiting in review the cards in the check lane of the linked projects

It says so in the bell, on your channels, and as a system notification when devpit is behind other windows. Pull requests are read with gh, in each project's folder.

Turning it on

Assistant mode is a toggle in the orchestrator chat's header, off by default and kept per orchestrator. On:

  • devpit writes .devpit/assistant.md in the orchestrator's folder and imports it into its CLAUDE.md, under the line that imports devpit's own brief. Off, both go, and every other line of CLAUDE.md stays as you wrote it. The brief is read when the chat next starts.
  • The chat gains its assistant's tools — its schedules, the heartbeat, the briefing and Telegram — without a restart.

The heartbeat

While Assistant mode is on, the orchestrator looks every 5 to 60 minutes. Settings → Assistant sets how often, and which of these it looks for:

  • a pull request whose checks fail;
  • a session stopped on a question for longer than a time you set;
  • a card in the doing lane waiting on a card that still holds it.

Nothing found, or nothing new, is silence. Something new is said once, not every time it is seen. With the mode off, nothing looks.

Telegram, both ways

What it tells you also goes to Telegram, under the channel event Your assistant has something for you. When it is a session stopped on a question, the message carries the question's choices as buttons, and a press answers it as a click in the Sessions panel would. The orchestrator can message you there too, within the chat's privacy setting.

Coming back

Back at the window after 30 minutes away, an orchestrator in Assistant mode shows three lines above its composer:

  • the sessions that ran, waited and ended;
  • the pull requests merged in its linked projects;
  • the decisions waiting on you: memory proposals, schedule proposals, drafts to send and Devflow plans to approve.

What it never does

It starts no work. A routine and the heartbeat only tell; a schedule is set only by your click; and everything in What it never does still holds.