Skip to content

samagotchi 0.92.0

Choose a tag to compare

@github-actions github-actions released this 19 Oct 21:54
· 3052 commits to main since this release

Added

  • A bundle's manifest can type its session settings (session_settings: {cap: number}: number, boolean,
    string or any); --set and POST /api/sessions refuse a value of another type (exit 2 / 400), and a
    string key keeps its text as given.

Changed

  • --set BUNDLE.KEY=VALUE (and bundle_settings strings in POST /api/sessions) type values as config.yml does:
    for a bundle that lists its keys plainly (or types them any), yes/on are now true, no is now false
    (any case: No, ON), and .5, 5., 1e3 are now numbers; before they reached the plugin as text. A bundle
    that wants the text types the key string.
  • Test kit: Samagotchi::Testing::Install.run(...).registered is an Install::Registered value
    (registered.commands, .tools, .hooks, .inits, .toolkits, .tool_sources, .peer_sources), its commands
    and hooks Install::Command / Install::Hook values, not a Hash of arrays: a bundle spec reading
    registered[:commands] needs registered.commands.
  • Test kit: Install::Result#ok? is gone; result.failures.empty? says the same.

Fixed

  • A Ctrl-C during a turn keeps what the turn did, as a Stop does: its finished tool calls and their results stay in
    the session with the cancel note (a call it cut short reads as interrupted), so the next turn knows what already
    ran and the note lists the background tasks the turn started. chi bundle try --timeout now shows that turn's
    tool calls with their arguments.
  • chi --help lists chi sessions restart, chi bundle trash and the bundle authoring subcommands (new, test,
    check, try).
  • Web: removing a queued message (its ×) and opening another session before the worker answered no longer puts the
    removed text into that session's composer; a toast names the session it came from and stays until
    dismissed, with Copy for the full text.
  • Web: images added to the composer while a message with images was still uploading or sending stay after it is sent,
    instead of vanishing with the sent ones.
  • Web: when the model list can't be read, the start page says so in a toast (a new session starts on the default
    model) instead of just leaving out the model picker.
  • --set cost-cap.cap=.5 and =1e1 set a cap (they were read as text and turned the cap off); --set cost-cap.cap=five is refused (exit 2) instead of silently running without a cap. A cap:, child: or default:
    in config.yml that isn't a number (or is infinite, 1e400) now warns once, and a bad cap:/child: falls back to
    the next one. Run chi update (cost-cap 0.2.1).
  • An attached-context wake turn stopped before the model call keeps its note as a plain one and pauses wakes until
    you write, as delegate and task wake turns do; it left the note marked as a turn's start.
  • A background task that finished just as the idle worker was about to exit still wakes the session (the worker
    stays up for its wake); one that finished before the worker left for another reason is a note for the next turn.
    A task whose turn you stopped no longer keeps the worker up or holds /exit.
  • chi send --wait on a session command delivered as a file reads the command's real outcome (failed, or canceled
    when it was refused mid-turn or dropped), not always completed, and says so as the command's ("the command
    failed"), not a turn's.
  • chi bundle try no longer signals its child's process group after the child exited (the group id may name
    another process by then), and no longer waits 0.1 s after every run. A --timeout stops the background tasks the
    turn started along with the child, and the delegate workers and tasks a run leaves behind are stopped before the
    sandbox is deleted.
  • chi bundle check warns (clash) about an installed bundle of the same name whose record can't be read, instead
    of skipping the clash check without a word.

Update with chi update (the system bundle 0.92.0, cost-cap 0.2.1, core 0.3.4), then restart chi web.