Skip to content

v0.44.0-beta

Choose a tag to compare

@github-actions github-actions released this 19 Nov 14:22
· 20 commits to main since this release
afc5b5c

What this release carries

  • The desktop's profile page leads with what a profile can and cannot do (#1120, #1121, Decisions 1060 and 1062): one sentence on what it is for, a rail with room right now, the model, the budgets, who it acts as, whether it asks first and Start; a card per server and one for Troupe's own tools, the refused ones struck through; what it cannot do, from the rules, the withheld servers and the hosts it reaches; the agents and skills as guidance; the configuration's tables folded away. The rail says the limits a session is held to in plain words: the output cap per model call, the model calls, working time and tokens before an agent asks to go on, how deep it delegates, when it sleeps, and the GitHub push caps. profile.get states them all; the harness's defaults live in one protocol module the harness reads too.
  • A bundle's author can write the profile's sentence, a server's subtitle and a line per tool (#1122, Decision 1063): an about key in the bundle, validated at publish, shown on the page in place of the defaults.
  • The console's "What a member sees" shows the same limits (#1131), in its own tables.
  • "Troupe is better in the app" moves to the app's browser build (#1118, Decision 1061): the web app opens #/session/<id> and #/artifact/<id>, writes the place to its address, and offers the installed app at that place; the console shell loses the line and keeps Open in the app per row; copied links name the web app beside the troupe:// line.
  • Archive from the session row's menu (#1116) and one control that folds every turn's working (#1117, Decision 1064), first in the session's menu, the same choice /detail makes.
  • The profile's room is counted the same in the listing and on the page (#1119): a gone pod counts for nothing in either.
  • A pod's streamed calls behind a LiteLLM gateway are priced (#1133, Decision 1065): the stream's usage.cost reaches the ledger, and the adapter asks the gateway for it; a profile needs no llm.prices for the gateway's aliases.

Before you upgrade a plane

  • No migration, no CRD change, no new setting. profile.get gains fields (limits, GitHub caps, harness tools, the two switches, about); nothing is removed, and older clients ignore them.
  • The bundle gains the optional about key; bundles without it publish as before. Upgrade the pods before adding a top-level about to a bundle: a worker from before this release refuses a bundle with an unknown top-level key; a server's about it ignores.
  • The console's shell no longer shows the "better in the app" line; the desktop app's browser build does. Links copied from the apps now name the web app (plane.app) beside the troupe:// line.
  • The desktop app's web build at /app now reads #/session/<id> and #/artifact/<id> from its address.
  • A pod behind a LiteLLM gateway sends x-litellm-include-cost-in-streaming-usage: true and charges the stream's cost; spec.llm.prices still applies to models the gateway does not price.

Installing

What this release carries

  • A profile's page says what it can and cannot do (#1124, #1130, Decisions 1060 and 1062): the desktop app's profile page leads with the room right now, the model, and what a session there can reach and use, instead of the configuration's seven sections in order. Its Limits say each limit a session is held to in a sentence ("Each model call writes at most 8,192 tokens.", "Delegates at most 3 levels deep.", "Pushes at most 20 times, then stops and says so on its pull request."), Troupe's own defaults included, and Troupe's card lists the harness's tools with the refused ones struck through.
  • The console shows an administrator the same limits (#1132): What a member sees gains Limits, the agents' own limits and GitHub tables, each limit with where it comes from.
  • A bundle's author can say what a profile and its tools are for (#1134, Decision 1063): a new about key, a sentence for the profile (200 characters at most) and, per MCP server, a subtitle and a line per tool (120 each). It is checked at validate, preview and publish, a tool the server does not carry is refused by name, it diffs in the preview, and the profile page shows it. The bundle schema stays 1, and a worker never sees it.
  • Calls behind a LiteLLM gateway are priced on the ledger (#1136, Decision 1065): a pod's streamed calls used to cost 0 unless the profile copied the gateway's prices into llm.prices. The OpenAI adapter now asks the gateway for the cost in the stream's usage and reads it from there, and the gateway needs no setting for this.
  • One control folds and unfolds every turn's working (#1128, Decision 1064): the desktop session view's ⋯ menu starts with "Fold every turn's working" or "Unfold every turn's working". It writes the same level /detail does, so moving one moves the other.
  • Archive from the session list (#1127): a row's ⋯ offers Archive session, and under the Archived filter it offers Unarchive session instead of a separate button.
  • The profiles list and a profile's page agree on the room (#1126): a gone pod no longer counts on the profile's page while it waits for the sweep, and a draining pod's running sessions count against the ceiling in both. All three counts come from one place now.
  • "Troupe is better in the app" moved to the desktop app's browser build (#1125, Decision 1061): the console has no twin in the app, so the line left it. The browser build at the plane's /app shows it and opens #/session/<id> and #/artifact/<id> addresses, and its link opens the same place in the app.
  • A flaky worker test got a longer budget for the plane's answer, though pods still wait two seconds (#1115).

Before you upgrade a plane

  • No migration, no CRD change, no values change, no new setting.
  • profile.get gains fields and removes none: about, harness_tools, github, personal_tools, memory_proposals, limits.max_tokens, limits.session, limits.idle_seconds, limits.budgets.team_period, max_turns and max_tokens on an agent, and about on an MCP server. profiles.list's fields keep their shape, but active_sessions now counts a draining pod's sessions. PROTOCOL.md has both.
  • A bundle may now carry about. A bundle that uses it cannot be published to a plane older than this one, so upgrade the plane first.
  • Behind a LiteLLM gateway the ledger starts showing what streamed calls cost, so team and profile budgets now count spending that read 0 before. A gateway is sent x-litellm-include-cost-in-streaming-usage: true even when a profile has identify: false, because it does not say who is calling. Vendor APIs and OpenRouter are not sent it.

Installing

Everything in this repository at afc5b5c, as one release, after the full suite.

On a cluster — the chart, whose images are this version, from the registry:

helm upgrade --install troupe oci://ghcr.io/it-minds/charts/troupe --version 0.44.0-beta \
  --namespace troupe-system --create-namespace --values my-values.yaml

or the same chart from this page:

helm upgrade --install troupe \
  https://github.com/it-minds/troupe/releases/download/v0.44.0-beta/troupe-0.44.0-beta.tgz \
  --namespace troupe-system --create-namespace --values my-values.yaml

Images, public and pulled without a credential: ghcr.io/it-minds/troupe-plane, troupe-operator, troupe-worker, troupe-a2a and troupe-gui, each tagged 0.44.0-beta. Installing has the CRDs, the values nobody can leave unset, and what the chart does not run for you.

On a machine — download the installer attached below, read it if you like, and run it. It installs this release: the daemon always, and it asks about the TUI and the desktop app.

Linux and macOS:

curl -fsSLO https://github.com/it-minds/troupe/releases/download/v0.44.0-beta/install.sh
less install.sh      # optional: read it first
sh install.sh

Windows (PowerShell):

irm https://github.com/it-minds/troupe/releases/download/v0.44.0-beta/install.ps1 -OutFile install.ps1
notepad install.ps1  # optional: read it first
powershell -ExecutionPolicy Bypass -File .\install.ps1

No questions: --tui --gui -y (-Tui -Gui -Yes). The VS Code extension: --vscode (-VSCode), or troupe.vsix below with Extensions: Install from VSIX…. Start over: --clean-install (-CleanInstall). Remove: --uninstall (-Uninstall). The desktop app's own installers are attached as well.

Then, in a new terminal, troupe config sets up a model (Enter at every question is Anthropic, with the key from ANTHROPIC_API_KEY) and troupe in a project directory opens a session; without the TUI, the desktop app sets the model up on This computer, under Models. The first run has both.