Repository navigation
Turns with many agents: the question and the answer in sight, one wait for all, no message lost, notifications - #22
Merged
Merged
Conversation
A turn that ended woke its agent again only for the person's messages. An answer from an agent it started, posted while its last call ran, waited unread until something else woke it, and was lost if iq started again in between, as the board's messages are not kept. A turn that ends now wakes its agent for what was written to it since it last read the board, as a message would have woken it resting: the person's, iq's, or that of an agent it started or one retired since, at once; a peer's at work under the same limit as when it rests, so that two agents writing to each other at their turns' ends do not wake each other forever.
An agent that starts several was woken, and read its whole conversation again, at every message they wrote: most of such an agent's calls were waits. `wait_for_messages` with `until_done: true` waits until none of the agents it started works, or one asks it something it has not read, ten minutes at most, then gives all they wrote at once, once the board stayed quiet 300 ms, as an agent rests just before its answer is posted.
…ges the strip A turn with half a dozen agents wrote every task and message between them into the conversation, several lines each, burying what the person asked and what they were answered. What agents write to each other, their tasks too, now stays out of the conversation, kept per chat for its turn. The turn's strip (`turn_view = "strip"`) shows the latest ten, a line each, the earlier counted. A turn of the person's chat in which other agents worked ends with one line that sums it up: the agents by model, the messages, the calls, the cost, and the key to every step. The summarizer is asked for one line of fifteen words at most. The steps' page still has everything whole. Not done: the panes show no messages, and an agent's line saying it joined stays in the conversation.
…aits
A long turn runs while the person is elsewhere, and nothing told them
it ended.
Ctrl-P (`notify` in `[keys]`) turns notifications on, before or during
a turn, and off again; the status line says so while they are on. A
notification comes as a question waits ("Waiting for you") and as a turn
of the person's ends, once none of its chat's agents works ("Turn done",
which also turns them off). Its words are iq's own, never the work's, as
a screen may be shared. It goes through the system's own tool, on a
thread of its own and with iq in front too, as the person may be away
from the screen: `notify-send` on Linux, which needs a notification
daemon, `osascript` on macOS, where a terminal's own escape showed
nothing until the system allowed its notifications.
The test of the messages kept out of the conversation waited for the summary of one of them only: the other, made on a thread of its own, could come later, and the test failed now and then.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Turns with many agents: a conversation that keeps the question and the answer, one wait for all, no message lost, and notifications.
What
wait_for_messageswithuntil_done: truewaits until none of the agents an agent started works, or one asks it something, ten minutes at most, then gives all they wrote at once, once the board stayed quiet 300 ms.turn_view = "strip") shows the latest ten, a line each, the earlier counted; a turn of the person's chat in which other agents worked ends with one line summing it up (agents by model, messages, calls, cost, the key to every step). The summarizer is asked for one line of fifteen words. The steps' page keeps everything whole. Not done: the panes show no messages, and an agent's line saying it joined stays.notify) turns on a notification of the system's as a question waits ("Waiting for you") and as a turn of the person's ends ("Turn done", which turns it off), shown in the status line while on, never a word of the work:notify-sendon Linux (which needs a notification daemon),osascripton macOS.Checked
Every commit passes
scripts/check.sh; the wake at a turn's end has a test that fails without it. Not checked live: the notifications (no notification daemon in the nested X server used), the strip and the turn's line with real agents.Stacked on #21: merge it first.