Skip to content

Grove 0.0.8

Latest
Latest

Choose a tag to compare

View all tags
@bearlike bearlike released this 21 Aug 22:40
0.0.8
3dfe12f

Grove's web dashboard touring the launch composer, the session browser, a workspace transcript beside its work panel, the usage audit and the fleet grid

A composer, not a dashboard

  • The landing route asks what you want to work on and starts a workspace from the answer.
  • Agent, model, runtime, project, working directory and branch are labelled controls under the textarea, each showing its own resolved value rather than a bare glyph.
  • Expanding the composer moves the one editor into a dialog instead of rendering a second copy, so there is only ever one draft and one tab stop.
  • The fleet keeps its own route, and the rail's New workspace opens the composer.

Public share links

  • Share a workspace read-only at a public link. The reader sees the transcript and the work panel, and nothing else.
  • The daemon serves those readers from three unauthenticated routes in their own namespace, never a hole punched in the authenticated one.
  • A link takes an optional passcode and a time to live, and prints to a branded page.

Shell completion

  • Completion for the grove CLI, with every completed value read from the config cascade rather than a baked-in list, so it describes the machine it runs on. It answers on the first tab.

Working directories and identity

  • A repository can declare labelled working directories and a default. The engine resolves it, so the CLI, the TUI, the daemon, MCP and issue ops all inherit it without changing.
  • A workspace's title and description are editable from the CLI.
  • The TUI saves create-form answers as defaults, selects a model per agent, and carries quota in its footer.

Fixes

  • A forked sub-agent's replayed record no longer duplicates its parent's tool call, which had been putting a repeated tool use id on the wire.
  • One unknown vendor no longer blanks every quota card.
  • The task board is scoped to its own session instead of being served to another.
  • The browser proxy exports the verb the share policy save needs, so saving a policy no longer fails.

Under the hood

  • Vendored front-end components from assistant-ui are pinned to an adopted baseline rather than diffed against a moving upstream, so the check still catches a hand edit without failing whenever upstream ships, and taking an upgrade is a deliberate step.
Assets 2
Loading