Rakumux v0.1.31

Rakumux 0.1.31

Your Sprite in the Agent feed

• Signed in, rakumux sprite connect (or N the first time) now connects your Sprite to your
  Agent feed too. Its agents' replies, chats and sessions reach rakumux.com and your other
  computers whether this one is on or not, and the replies you write to them there are typed in.
• It asks once whether replies you write on rakumux.com are typed into the Sprite's agents
  (--replies or --no-replies answers for you).
• The Sprite never holds your sign-in: this computer enrols it, and rakumux.com gives it access of
  its own for 15 minutes at a time. rakumux sprite disconnect, or Revoke on rakumux.com's
  Features page, cuts it off.
• rakumux.com wakes a paused Sprite when you write to one of its sessions, and the Sprite stays up
  long enough to type your reply in. It also stays up a minute after its agents finish, so their
  last replies leave.

Upgrading

U installs the update and reloads the UI. For a Sprite you connected before, run
rakumux sprite connect again, signed in: it updates Rakumux there and connects its feed. The
server here hasn't changed in a way that matters off a Sprite, so there's nothing to restart.

Rakumux v0.1.30

Rakumux 0.1.30

Restarting the server restarts its services

• S (or Settings → Restart server) now restarts the account service and the local API
  (rakumux-api, which the phone app and agents' Rakumux tools use) too, on the same build, once
  the server is back. Before, both kept running the version they started with until restarted by
  hand.
• A window started before Rakumux was rebuilt or updated could fail to start the account service
  from its old binary; it now starts the new one.

Upgrading

U installs the update and reloads the UI, and the account service replaces itself with the new
version. The server hasn't changed since 0.1.29, so there's nothing to restart.

Rakumux v0.1.29

Rakumux 0.1.29

Sessions on your own Fly.io Sprite

• Press N (or click ☁ Sprite at the right of + New session) and new sessions in that folder
  run on your own Fly.io Sprite: a Linux VM that pauses when nothing
  happens and keeps its files. n then starts one there. N again brings the folder's new
  sessions back to this machine.
• The first time, Rakumux sets the Sprite up with your Sprites token: one the sprite CLI saved
  on this computer, or one you make at sprites.dev/account and paste. It creates the Sprite,
  installs Rakumux there and connects, step by step. The token stays on this computer; the Sprite
  gets a Rakumux token of its own.
• A session on the Sprite has ☁ before its name and is listed under the folder you started it
  from. Going in is its live terminal on the Sprite. It runs in a folder of the same name in the
  Sprite's home, and for a git repository git clone <origin> . is typed there for you to run.
• While an agent works on the Sprite, Rakumux keeps the Sprite from pausing. Once none is, it
  pauses and costs little, and its sessions come back when you open one.
• From the command line: rakumux sprite connect sets the Sprite up, rakumux new --sprite runs
  a session there, and rakumux machine add | ls | rm lists the sessions of any other machine
  running Rakumux here, through its rakumux-api remote listener.

Also

• rakumux-api serves /v1/daemon on its remote listener: the server's own protocol, for another
  machine's Rakumux.
• A server started without SHELL (as a service) starts your login shell in new sessions, not
  /bin/sh.

Upgrading

U installs the update and reloads the UI. Sessions on a Sprite need the new server: press S in
Rakumux mode, then y (or run rakumux daemon restart) to restart it in place. Your sessions keep
running.

Rakumux v0.1.28

Rakumux 0.1.28

Top

• Settings → Top (or t in Rakumux mode) shows the machine's CPU, memory and network, then this
  window, the server, the other clients and every live session with its processes as a tree,
  about every second while it's open. Nothing is recorded. Network per process is Linux only;
  macOS shows CPU and memory per process.

A session's age is its last prompt or reply

• The age beside a session is when its agent last had a prompt or wrote something, by the
  conversation's own clock, kept after the agent exits. Before, it was when you last went into
  the session, and a server that came back after a crash or reboot made every session it revived
  look active then. Sessions without an agent show when they were last used, as before.

Selecting text stays in its pane

• Drag over a session's preview, a session whose program doesn't use the mouse (a shell, say) or
  the terminal panel to select its text: it stays in that pane and is copied when you let go.
  Shift-drag, your terminal's own selection, ran across the session list. Claude Code uses the
  mouse, so inside its session it still gets the drag: drag over its preview in Rakumux mode
  instead.

Replies

• A reply that went in while the agent was already working (Claude Code queues it) counts as
  delivered. Before, it could say it wasn't taken although the agent had it.
• A reply written in the feed waits behind ones written a moment before on rakumux.com that this
  machine hasn't read yet, so they go in the order they were written.

Upgrading

U installs the update and reloads the UI, and the account service replaces itself with the new
version. Top, the new session ages and the replies change need the new server: press S in
Rakumux mode, then y (or run rakumux daemon restart) to restart it in place. Your sessions keep
running.

Rakumux v0.1.27

Rakumux 0.1.27

A reply says when it didn't go in

• A reply from rakumux.com or the feed counts as delivered only once its agent's chat shows it as
  a new prompt. One whose Enter was lost, or that landed in a menu, now says it wasn't taken and
  may still be in the session's input box. Before, every reply counted as delivered 30 seconds
  after it was typed in.

Sent once, however often you send it

• A reply written in the feed and sent again after an error (a time-out, say) is stored and typed
  in once. Before, the second try could put it in twice.
• Replies being typed in, and replies you write in the feed, no longer wait behind file downloads
  and AI titles.

Upgrading

U installs the update and reloads the UI; the account service is replaced by the new version by
itself.

Rakumux v0.1.26

Rakumux 0.1.26

Replies from rakumux.com arrive at once

• Signed in with the Agent feed on, the account service keeps a connection to rakumux.com and
  reads your replies the moment you send one, instead of checking every few seconds. It still
  checks once a minute in case a nudge is lost, and checks as before while the connection is down.
• The connection carries nothing but "read now": your replies still come over the usual request.

Typed in once, and only into the agent

• A reply is typed in at most once. Before, the account service being replaced (by an update, for
  one) while a reply waited to be reported could type it again.
• A reply meant for an agent that has just quit stays at the shell's prompt instead of being run
  there as a command. This needs the server restarted in place (below).
• Each reply keeps its own answer: replies typed in one after another each get theirs, and one
  whose turn ended without an answer (interrupted, an API error) no longer takes a later one.
• Only replies written in this machine's TUI skip Settings → Replies from rakumux.com; before, a
  reply from elsewhere could claim to be one.

Machines with the same name

• Each machine now keeps a name and an id of its own. Two machines with the same hostname, or two
  Rakumux homes on one machine, no longer read each other's replies or replace each other's
  sessions on rakumux.com: the second takes the name with a few characters after it.
• A machine whose hostname changes keeps its name on rakumux.com, so replies to it still arrive.

Upgrading

U installs the update and reloads the UI; the account service is replaced by the new version by
itself. To keep replies out of a shell, restart the server in place too: press S in Rakumux
mode, then y (or run rakumux daemon restart). Your sessions keep running.

Rakumux v0.1.25

Rakumux 0.1.25

AI session titles

• Signed in with the account's AI session titles on, each agent chat gives its session a short AI
  title, once its agent has written 5 messages or its turn ends. A name you gave (r) stays.
• s, or the ↻ after a hovered session's name, makes a new title; a spinner shows there while
  it's made. A title another session of the folder has gets 2, 3, …
• Titles replace AI descriptions: the line under each session's name is gone, and so is your last
  message shown there before one. rakumux account status still lists each session's description.
• AI session summaries are now called AI session titles, in Settings → Available on sign-in, the
  account dialog, Help and on rakumux.com. rakumux account status --json adds
  ai_session_titles and keeps ai_session_summaries.
• While the account's titles are on, local AI naming (your Anthropic or OpenAI key) steps aside.

A tidier list

• Under Status, ready's last hour, last day and older headers and their sessions sit one
  column in from ready.

Upgrading

U installs the update and reloads the UI; the account service is replaced by the new version by
itself. If your server predates 0.1.24, restart it in place too: press S in Rakumux mode, then
y (or run rakumux daemon restart). Your sessions keep running.

Rakumux v0.1.24

Rakumux 0.1.24

Places name their repository

• Each place shows its repository's name before the branch: focal-md-paper-links focal-md ⎇ paper-links. The name comes from the repository's origin remote, else its main checkout's
  folder, read from .git files on this machine. A checkout named like its repository doesn't
  repeat it.
• Where a session works now is one line again, in line with the session's name and description:
  its path, then its repository and branch. Short of room the path is cut from its start first,
  then the repository's name, then the branch.
• Its other places (w, W, or a click on ▸) sit two columns further in, a divider above each,
  with no bars beside them.

A tidier list

• Session rows line up with their header: folder, app and status names, pinned and every
  session's text start in one column, and the marks (the pin toggle, the summary's ↻, the places'
  ▸/▾, the copy mark) sit in a margin on the left.
• Under Status, ready's last hour, last day and older headers line up with ready instead of
  a step in.
• The working spinner turns faster.

Help

• The w/W note says what goes to rakumux.com: with the Agent feed on, places' names, branches
  and times, never full paths.

Fixes

• The list's ages, on rows and places, come from the list's own clock, the one that sorts ready
  into its periods, so the two always agree.

Upgrading

U installs the update and reloads the UI. The server reads the repository names, so restart it
in place after updating: press S in Rakumux mode, then y (or run rakumux daemon restart).
Your sessions keep running. Places kept from before get their repository's name the next time the
session works there.

Rakumux v0.1.23

Rakumux 0.1.23

The Feed beside your sessions

• The Feed is now a pane beside the session instead of a view in place of the list. It's hidden
  when Rakumux starts and opens only when you ask: press f, or the footer's ≡ Feed button.
  Press f again while it has the keys to hide it; Esc gives the keys back to the list.
• Drag the line on its left to resize it. It needs room beside the session, so b (hiding the
  list) makes some. In a narrower window it takes the session's place in Rakumux mode only, so the
  session you're typing in keeps its full width.
• Grid shows it beside the cards, Tabs gives it a Feed tab at the start of the tab bar, and on a
  phone it fills the screen.
• Enter reads a reply whole, and Enter again goes into its session when it runs here.

Write to an agent that's still working

• A prompt still waiting for its answer (a working card) can be answered now: r writes back on
  a session's newest card, whatever it is. Your message joins its chat's thread, or, when the
  chat has nothing to reply to yet, goes to the session itself, as it does on rakumux.com.

Messages from rakumux.com, one at a time

• Two messages sent to a session close together could reach its agent as one prompt. Rakumux now
  types them one at a time, in the order you sent them, and waits for the agent to take each one
  before typing the next.
• The Enter now goes in on its own, half a second after the text. Claude Code dropped an Enter
  that came with a message ending in an image's path, so a message with an image attached stayed
  in its prompt and went with the next one.

Where each session has worked

• Each session in the list shows the folder it works in now and its branch, and follows its agent
  into a worktree.
• When its agent has changed files in other git working trees too, ▸ beside it opens them:
  press w (W for every session) or click it. Each shows its path, its branch and when, most
  recent first. Folders it only started in or read from aren't listed.
• y, or a click on a place, copies its path. While they're open, ↓/↑ step through them.
• Places are read on this machine from what the agent did. With the Agent feed on, rakumux.com gets
  their names within the session's folder and their branches, never full paths.

The footer

• The footer names the session on the left and the mode in the centre (RAKUMUX MODE, SESSION
  MODE, TERMINAL MODE), with the buttons on the right. A tap on the mode still switches it.

Fixes

• Esc acts at once on a desktop terminal over SSH. It waited up to 800 ms for the rest of an
  arrow key; only phones over SSH, whose keys can arrive in pieces, still wait.

Upgrading

U installs the update and reloads the UI, and the AI status service replaces itself with the new
version. Places and the Enter on its own need the new server: press S in Rakumux mode (or run
rakumux daemon restart) to restart it in place. Your sessions keep running.

Rakumux v0.1.22

Rakumux 0.1.22

Files with your messages

• Files you attach to a message or reply on rakumux.com now reach your agent. Once the agent is
  waiting for you, Rakumux downloads them into ~/.rakumux/uploads/ and types your message with
  each file's path on its own line, so the agent can open them.

The Feed is a view of its own

• Press f, or the footer's ≡ Feed button, to switch between your sessions and the Feed. Esc
  goes back to your sessions. The list's tabs are now Status, Folders and App.
• From session mode, a click on a card in the Feed opens it at once, as Enter does.

More room for the session

• In Master detail, « Hide list at the foot of the list, or b, hides the list so the session
  takes the whole width. Click the rail on the left or press b again to bring it back.

Steadier tabs

• Session tabs (the Tabs layout, and on phones) keep their places as sessions work and are read,
  so cycling through them reaches every session. When they don't all fit, the ends of the bar say
  how many are hidden.
• The list's tabs keep their names in a narrower list.

Fixes

• On an account with more than 100 replies, Rakumux could skip replies waiting for this machine
  and never type them in. It now reads every page.
• A failed read no longer holds up telling rakumux.com that a reply was typed in, so it isn't
  marked undelivered.

Upgrading

U installs the update and reloads the UI, and the AI status service replaces itself with the new
version. The server hasn't changed since 0.1.21: if you restarted it then, there's nothing to
restart. Otherwise press S once, so replies wait while you type. Your sessions keep running.