OpenRemote 0.4.7

Chats you can arrange, and a Browser section that says what the browser keeps.

Three things the console had no way to do, all of them about the lists you live
in all day.

Added

• Move a chat to another project. The chat's own row menu has Move to
  project, which opens this machine's project picker where the menu was, with No
  project first and the chat's current project marked. A chat with a turn in
  flight is refused in the daemon's own words; a running chat that is between
  turns restarts its harness in the new folder, and the transcript keeps a line
  saying where it moved. Whether the agent's own conversation continues depends
  on its harness: one that finds its session record continues where it was, and
  one that does not starts a fresh conversation in the new folder.
• Pin a chat. Pin, from the same row menu, keeps a chat at the top of its
  project's list, in the order you pinned them, with a pin mark on the row.
  Unpin puts it back where its activity puts it. Pins are this computer's
  arrangement, not something the account carries.
• Lists that page. A project draws five chats and the flat Chats list
  fifteen, with a quiet "Show N more" line that opens the rest of that list for
  the session. Nothing is hidden that you cannot get back in one press.
• Settings > Browser. What the browser keeps on this computer, in one place
  and in plain words: how many bookmarks, how many pages read, that a private
  tab is never recorded, that cookies and site data live in the profile the
  pages share, and where downloads land. Clear history and Clear bookmarks ask
  once, the way the other destructive rows do. Two rows say where the work is
  done instead of offering a button that would do nothing: the shell clears site
  data tab by tab, and the downloads list is the browser's own page.

Known

• An installed app still does not look for a newer version. Moving to a newer
  release means running a newer installer over it, or openremote --update if
  you installed through npm.
• A chat moved between projects is not moved from another device: the route is
  local to the daemon that runs the chat.
• Bookmarks do not follow you to another computer yet, and neither do the pages
  you read. The daemon can already carry browser settings and bookmarks between
  your devices, but the console keeps its bookmarks in its own storage and does
  not write them there yet, so nothing about them leaves this machine.