Repository navigation
v0.8.40
0.8.40 updates from 0.8.0 or later. From 0.7.x, start 0.8.0 once first:
Upgrading to 0.8 has the way across.
On Docker, check your configuration with the new image before you switch:
docker run --rm -v ./nouride:/app/.nouride ghcr.io/nouverse/nouride:0.8.40 nouride config check, with the volume your
compose file mounts.
A release about missions. The Missions page is a board: what is planned, what is at work, what needs you, and what is
finished under them. A mission an agent starts is a draft you start, a mission's own page is laid out from the top, and
its report can hold pictures. With it: a browser for agents in the Docker image, a Home app on the same machine that
stays signed in, and a fresh chat that offers what its agent can make.
Missions is a board
The page was tabs of one long list, and a draft was counted among what needs you.
- Three columns hold what is still open. Backlog, the drafts. Working, what is queued, running or being
checked. Needs you, a question, approvals, a limit reached or a result to accept. - Finished is a list under them, a row each for what is done, failed or stopped, with why it failed or who stopped
it. It goes back 7, 14, 21 or 30 days (7 unless you choose), and Done, Failed and Stopped narrow it. - A card says what matters: its name, a bar of its checklist's progress, one line (when a draft is done, the step
it is on, what it asks), the agent and when. Start on a draft and Answer on a question work from the card.
A card and a finished row open their mission wherever you press them. - Every column shows its newest five, with Show more under them. What is open is listed however old it is.
- With nothing open, the three columns are one thin line and Finished has the page.
- Hover a time for the day and the minute a mission was made, started and ended.
- On a phone the board is four tabs with their counts, opening on Needs you when anything is there.
- New mission has two buttons. Save to backlog keeps it as a draft until you start it, Start now starts it
at once. - A draft is deleted at once with Delete on its page, with its folder: nothing of it has run.
- A draft is no longer counted as waiting for you, on Home, on Work or in the list.
A mission an agent starts is a draft first
An agent told "do it, I'm off to sleep" could start a mission at once, with a goal and checks nobody had read.
- Every mission an agent starts is a draft. It drafts it and says so. You start it with the button, or tell the
agent to go and it starts its own draft on your word. /mission <goal>asks the agent you address for a draft of that goal. It reads what it needs, writes the brief
and the checks, or asks first when the goal is unclear. It used to start the mission from the goal's words alone./goalis the same command as/mission, with every one of its forms.- A mission you write on the dashboard's form with Start now, and an automation's mission step, still start at
once. - An agent can be asked what is in its backlog. It answers for its own missions, the ones it works and the ones it
drafted for another agent: every one still open however old, a draft named as a draft that has not started, and the
last twenty that ended. A draft used to read to the agent like a result waiting to be accepted, and an old one fell
off the end of its list.
A mission's own page
- What it does now and how far it is are at the top, under its name: the step at work, the checklist, the turns,
the hours and the tokens against their limits. - Its brief and its result have the page's width. The brief is folded to its header until you open it.
- Its checklist is over its turns, with its folder, what decides it is done and the box to tell it something beside
them. What decides it is done is folded to one line ("10 checks pass, then you accept") and opens by itself when a
check failed. - A long checklist shows the five steps around the one at work, and the turns their newest five, with the rest a
press away. - A draft's page has only what you can change before it starts, and says Draft.
A report that is not all text
- A picture a mission hands back is drawn in its report. When the report names a picture that is among the
mission's own result files (), the page draws it there, in the Result card and in the report
opened whole. PNG, JPEG, GIF and WebP. Any other name stays its words, and a picture on the web still waits for a
press. - A mission is told how to write its report: what came of it first, a table for a list of things with a state, and
a picture where the work has a shape. - The diagrams skill draws a diagram as a page where a browser is already set up, renders it, measures it (text cut
off, text over text, text too small, low contrast, anything past the picture's edge) and fixes what it finds before
sending the picture. Without a browser it draws with Graphviz, as before, and never installs a browser for a diagram.
A browser for agents in the Docker image
In Nouride's Docker image an agent asked to open a page had no browser, could not install one the way the browser skill
said, and answered from search results without saying so. Reported in issue #25.
- The agent installs the system's Chromium and Node as system packages, asking first as it does for any package,
and they are there again after the container is recreated. Chromium takes about 300 MB. - Where it cannot get a browser it says so first, instead of doing the task without one.
A Home app on the same machine stays signed in
Nouride Home on the machine the daemon runs on landed on the sign-in page each time its session ran out.
nouride auth device --name "Nouride Home"prints a device token, once. The app trades it for an ordinary
dashboard session whenever it is signed out. It is made only from the command line of the machine itself, and is
bound to the first admin account.- An admin sees each one on the Users page and takes it off there, which also ends the session the app is using.
- A wrong token counts against the same limit as a wrong password.
nouride users resetremoves the tokens with the
accounts, and changing a password leaves them. - This is Nouride's half. The Home apps use it from a release of their own.
A fresh chat offers what its agent can make
A new chat offered the same four things to every agent, a carousel and a mockup among them, whether the agent had those
skills or not.
- The work a fresh chat offers is drawn from the agent's own skills: a carousel, a mockup, a diagram, slides, a PDF
report, a chart, research with sources and others. Two are shown, and another chat offers others. - An opener is offered only where the agent has the skill and its machine has what the skill needs. An agent with none
of them is offered no work.
Fixes
- A chat no longer shows its agent typing for as long as a coding CLI works by itself. An agent on Claude Code that
went on by itself in a chat, with a step it never ended, held the chat as "typing" for an hour. A step with nothing
said for five minutes now goes on behind the turn: the chat is free, the step is not reported as failed, and the
agent's next words come to the chat as before. - "Got it" has its switch on the dashboard. Agent Settings has a card, While an agent works, with both
switches: the quick "Got it" when a message arrives while the agent works, and the agent's own line. 0.8.39 had the
first inconfig.tomlonly. - A command sent to a chat with no message yet leaves nothing behind.
/statusas the first thing in a new chat
left a record that deleting the conversation could not remove. - No blank band under a mission's page. Scrolling at the page's end pushed the whole dashboard up and left an empty
band as tall as half the window. - A draft that never started is not remembered as something you did. A draft dropped or deleted left "Mission
stopped" in its person's memory, for a mission of which nothing ever ran. - A folded card's arrow lines up with its title, on a mission's Brief and Done when, and the press that shows the
rest of a turn's reply starts at the reply's own edge.
Before you upgrade
Nothing to do first.
Full Changelog: v0.8.39...v0.8.40