Repository navigation
Releases
STELLA v2.0.1
Sessions that last. A session in a private project now stays open when
everyone has left, so a crashed agent no longer costs a participant their
invitation, and STELLA Jev no longer runs out of memory after about an hour.
Also: the participant link as a QR code, and setup dialogs that ask before
throwing away what you entered. Ships Agent SDK 0.10.1.
Upgrade notes
- Back up the database before you upgrade. This release applies one database migration on its own during the deploy (whether a project or session closes when everyone has left, and when a session was kept open). Nothing backs up for you first
- Sessions in private projects, existing ones included, no longer close when everyone has left. Public projects keep closing empty sessions. Switch a project in its settings ("When everyone has left") if you want the other behaviour
- Redeploy running STELLA Jev agents after the upgrade so they run the fixed image; a running agent keeps the image it started with
- Rebuild uploaded agents to get the memory fix. They keep working without it, but only an image built with Agent SDK 0.10.1 has it. Agent SDK 0.10.1 is on PyPI before this release reaches production
- No new required setting
Added
- The participant invitation link now shows as a QR code too, in the invite dialog and in a participant's connection info, so a phone can scan its way in instead of typing the link. Revoking an invitation greys the QR out the same way it already did the link (#921)
Changed
- A session no longer closes when everyone has left. Before, once the
participant and the agent had both gone, the session closed and the
participant's invitation stopped working, so a crashed agent cost a study
participant their place. Now a session stays open and the invitation keeps
working. The sessions list shows that everyone has left, with a Restart
agent button that starts the agent again with the settings it had. A
project's settings ("When everyone has left") can switch back to closing,
and Edit Session can set it for one session. This applies to existing
private projects too. Public projects, existing ones and new ones, close
empty sessions instead, because every visitor starts their own session;
the choice can be changed during setup or in the project's settings.
Closing a session yourself, or reaching its maximum length, still closes
it. (#920)
Fixed
- Deploying an agent or inviting a participant now asks before discarding what you started. Clicking outside the dialog, pressing Escape or the close button only closes right away when nothing was entered; otherwise it asks to keep editing or discard, the same guard the Agent Configurator already had (#919)
- STELLA Jev no longer runs out of memory after about an hour. Each time a participant's audio reconnected, the agent kept the old audio stream filling up in the background, so a long session reached its memory limit and the agent was stopped. The agent now closes the old stream, and the incoming audio queue holds at most 30 seconds (
STELLA_AUDIO_QUEUE_MAX_FRAMES). The fix is in Agent SDK 0.10.1, so every built-in agent has it, and uploaded agents get it with a rebuild (#922) - Agent SDK 0.10.1 (
pip install stella-ai-agent-sdk==0.10.1), fixes only: audio streams are closed on unsubscribe and the incoming audio queue is bounded. Details in the SDK changelog
STELLA Agent SDK 0.10.1
Install with pip install stella-ai-agent-sdk==0.10.1.
Production 2.0.1-21-g2b7b2a4d
What's Changed
- chore(release): 2.0.1 changelog and version, Agent SDK 0.10.1 by @DatMoser in #936
- docs: 2.0.1 upgrade notes, version label, sessions kept open when empty by @DatMoser in #937
- S8 batch by @DatMoser in #934
- fix(sdk): close audio streams on unsubscribe and cap the audio queue (#922) by @DatMoser in #931
- feat(sessions): keep a session open when everyone has left (#920) by @DatMoser in #932
- Ask before discarding agent or participant setup on an outside click by @DatMoser in #933
- feat(invite): show the participant join link as a QR code too by @DatMoser in #935
- release: 2.0.1 by @DatMoser in #938
Full Changelog: prod/2.0.0-20-g36dc8515...prod/2.0.1-21-g2b7b2a4d
Production 2.0.0-20-g36dc8515
What's Changed
- feat(agents): one agent interface, the deploy wizard and ELIAS-Interviewer (#867 + #868 + #854) by @DatMoser in #869
- Client channel and the Text face (#92) by @DatMoser in #870
- Agent picker: cards fit their content, upload lives in the Agent Library by @DatMoser in #871
- Agent Library: name the projects a shared agent can be deployed in by @DatMoser in #872
- Deploy wizards: size the dialog by the screen, not by the step by @DatMoser in #873
- Connectors as a grid, with a detail page to test each tool by @DatMoser in #874
- Uploaded agents get a LiveKit token for their own room only (#856) by @DatMoser in #876
- STELLA Jev as a built-in agent on manifest 2.0 (#849) by @DatMoser in #878
- feat(agents): agent.yaml as the single source of truth for the agent platform by @DatMoser in #864
- S6 batch by @DatMoser in #831
- fix(test): delete the NestJS scaffold e2e test by @DatMoser in #823
- fix(agents): clear healthState when an agent stops by @DatMoser in #824
- feat(agents): let users deploy their uploaded agents; admin review becomes a switch by @DatMoser in #851
- feat(connectors): per-user MCP connectors agents reach through the backend (PR 2) by @DatMoser in #855
- fix(kubernetes): keep agent pod requests within their limits by @DatMoser in #858
- feat(agent-package): agent manifest 2.0 as the single source of truth (1/5) by @DatMoser in #860
- feat(sdk): 0.10 platform contract; built-in agents move onto it (4/5) by @DatMoser in #862
- feat(agents): deploy enforces what the agent manifest declares (2/5) by @DatMoser in #861
- feat(agent-image): built-in images and the SDK window from the manifest (3/5) by @DatMoser in #863
- Batch: 644, 830, 832, 833, 834, 835 into development (2.0.0) by @DatMoser in #885
- fix(v2): keep the bridge when a safety override replaces the reply by @DatMoser in #644
- fix(mcp): sessions_get's messageCount counts transcript lines only by @DatMoser in #830
- fix(deploy): remove untagged containerd image digests after rollout by @DatMoser in #832
- fix(mcp): point agent-configuration tools at agent_types_get for the schema by @DatMoser in #833
- Typed agent settings in tabs, template checks (#585) by @DatMoser in #834
- Show when Stella is still getting ready to listen (#564) by @DatMoser in #835
- chore(release): 2.0.0 changelog and version, Agent SDK 0.10.0 by @DatMoser in #882
- docs: 2.0.0 docs match what shipped, version label and upgrade notes by @DatMoser in #886
- chore: S6 batch v4 — Agent Review (#900, #901), SDK doc examples (#902), auto-build on upload (#906) by @DatMoser in #905
- feat: Settings → Agent Review, where system admins approve or reject uploaded agents (#897) by @DatMoser in #900
- docs(sdk): examples that import against SDK 0.10.0, one SDK section, and a CI check (#887) by @DatMoser in #902
- Uploaded agents build automatically after upload, with the build status on the card by @DatMoser in #906
- docs+ui: Agent Review nits from the PR 900 review (#897) by @DatMoser in #901
- docs(changelog): 2.0.0 covers Agent Review, auto-build on upload and the SDK docs merge by @DatMoser in #907
- feat(wizard): pick the env-var template on one screen, adjust the settings tabs on the next (#892) by @DatMoser in #910
- release: 2.0.0 by @DatMoser in #888
Full Changelog: prod/1.5.0-19-gb1e12a94...prod/2.0.0-20-g36dc8515
STELLA v2.0.0
The agent platform. Anyone can now write an agent with the Agent SDK, describe
what it needs in its agent.yaml, upload it and run it in a session. STELLA
holds no code for any one agent. Agents can use outside tools through
connectors, which each user sets up in Settings, and the credentials never
reach the agent. Participants can hold a whole conversation in writing on the
new Text face. STELLA Jev joins as a third built-in agent, and the ELIAS
interviewer is the first uploaded one. If you upgrade, read "Upgrade notes"
first: agents uploaded before this release need one rebuild.
Upgrade notes
- Back up the database before you upgrade. This release applies seven database migrations on its own during the deploy (connectors, connector icons and descriptions, the agent manifest, the agent's SDK version, sharing uploaded agents with projects with a backfill, and a column marking which configuration templates have been checked). No template data is changed, and nothing backs up for you first
- Rebuild every uploaded agent once after upgrading. STELLA now records which SDK an agent's image contains and refuses to deploy an image whose SDK it doesn't know, so agents built before this release can't be deployed until they are rebuilt from Settings → Agent Library. Agent SDK 0.10.0 is on PyPI before this release reaches production, so the rebuild works straight away. On production this includes ELIAS. Built-in agents are unaffected
- Uploaded agents need Agent SDK 0.10.0 (
MIN_SUPPORTED_SDK_VERSIONis 0.10.0). Built-in agents are built with it from the repository - A deploy without a required env var is now refused up front with a 400 that names it, instead of starting a pod that then fails. Check that each built-in agent's required keys (for example
OPENAI_API_KEY) are set - "Review uploaded agents" is on after the upgrade (Settings → Platform Defaults), so a system admin approves each upload before it can run
- No new required setting for the platform itself
Added
-
ELIAS-Interviewer, the first uploaded agent (
custom-agents/elias-interviewer, Agents → ELIAS-Interviewer). It runs an ELIAS interview guide in a voice session: it asks every question word for word, asks an unclear answer again up to three times, and writes each turn to ELIAS as it happens. It reaches ELIAS only through a connector, so the ELIAS token never reaches the agent. It is uploaded and deployed like any custom agent -
Uploaded agents can be deployed into a session. Before, any agent type other than the built-in STELLA V2 and STELLA Light was turned away at deploy time. Now an uploaded agent deploys once a system admin approves it, and its pod runs the build's own start command. A rejected agent never deploys, including on restart or wake after auto-pause.
-
Admin switch: "Review uploaded agents" in Settings → Platform Defaults. It is on by default, because building an upload runs its Dockerfile on the server and the agent's code runs in sessions unreviewed. A system admin can turn it off; then a user can deploy their own upload as soon as it is built, and other users still need an admin's approval.
-
Uploaded agents belong to their owner and are shared per project. In Settings → Agent Library the owner picks the projects an upload is shared with; members of those projects see it marked "Shared by …" and can deploy it there only. Only the owner can build it, upload a new version, change its sharing or delete it. The upgrade shares each existing upload with the projects that use it as their public agent or have it running or paused; every other upload starts private to its owner
-
A new version replaces your agent in place. Uploading the same
metadata.slugwith a highermetadata.versionkeeps its env var templates, configurations, shares and public projects pointing at it; the new version must be built (and approved, if review is on) before it deploys -
Delete an upload from the Agent Library. It is refused while the agent still runs in another user's session or a public project uses it, and the message says how many
-
Participants and researchers see when STELLA is still getting ready to listen. After a quiet spell, speech recognition can take up to about 30 seconds to warm up at the start of a session. The participant now sees "Getting ready to listen…" (in German or English), and the researcher sees an "STT warming up" chip with a timer. After 30 seconds it says it is taking longer than usual, and if warming up fails the participant is asked to tell the study team. Nothing shows when the model is already warm (#564)
-
STELLA Jev (
stella-jev-agent), a third built-in agent (#849). STELLA V2's pipeline without the bridge: one Jev call decides the experts and barge-in, and the agent asks back when what it heard isn't believable (the common-sense expert). The reply no longer waits for task extraction, which saves the answer in the background. Take-back: if someone carries on speaking after their turn was closed and before any of the reply was heard, the reply is dropped and the joined-up words are answered, and nothing from the dropped reply is saved (take_back_window_mson the new Turn Taking node, 0 is off). It sends conversation text to TypeSafe and needsTYPESAFE_API_KEY. It is seeded and built fromagents/stella-jev-agent/like the other built-ins, with no agent-specific code in STELLA. -
Connectors in Settings as a grid of cards, like personas and plans. Each connector has an emoji and a description (new nullable
Connector.iconandConnector.descriptioncolumns, also on the MCPconnectors_createandconnectors_updatetools). Its detail page lists the tools from the last test with their parameters, has Try it to call a tool for real with the owner's token (audited like an agent's call), and shows the connection, sharing and recent calls. New endpoints:POST /me/connectors/:id/tools/:tool/callandGET /me/connectors/:id/calls, both owner-only. See Agent SDK → Connectors. -
Text face for participants (#92). Text is one of the faces in the participant's face gallery: the whole conversation in writing. Replies show as the agent sends them: streamed if it streams, whole if it doesn't. While it shows, the agent answers in text only, speaks nothing and does not wait for speech, and the microphone is off. Picking any other face switches back to voice, and the microphone comes back if the switch took it. Speech-to-text and text-to-speech stay connected, so switching is instant. An invitation locked to the Text face is a text-only session: the join page skips the microphone setup. The chat drawer on the voice faces stays as a fallback for typing next to speech. See Guides → Text sessions.
-
A declared channel between the screen and the agent.
agent.yamllists the events the screen may send (client.events) and the commands the agent may send (client.commands), with a JSON Schema for each one's data. Anything else is refused. The screen can ask for an answer and gets the agent's reply. Every event, reply and command is kept in the session history. See Agent SDK → The platform contract. -
Agent manifest 2.0 (
agent.yaml). An agent now declares what it needs in its own blocks:features(persona, plans and their modes, configurator),env(required and optional env vars) andconnectors. Anything a deployer chooses is anenvvariable;configSchemaonly describes the agent's fixeddefaultConfig. Manifest 1.0 still works and is upgraded on read, with a deprecation warning. A published JSON Schema (docs-site/static/schemas/agent-manifest.v2.json) gives editors completion and validation. See Agent SDK → The agent manifest. -
Deploy enforces what an agent's manifest declares. One check runs on every deploy, restart and wake after auto-pause, and refuses the deployment with a 400 that lists every problem:
- A required env var is missing or empty.
- The agent runs plans and has neither a plan nor a companion session.
- A plan, companion session or Configurator configuration is given to an agent that doesn't declare it.
- The agent needs a configuration (
features.configurator: { required: true }) and has none. - The agent needs a newer SDK than this STELLA ships.
- A deployment tries to set agent settings beyond the platform keys (persona, mode, plan, configuration); those are env vars now.
- An env var value doesn't fit its declared type, range or options.
Before, only a stella-v2 rule hard-coded in the backend was checked. The agent's
defaultConfignow reaches the pod, where it used to be dropped. Pods get the manifest's resource requests as well as its limits. -
GET /agent-typesreturns each type'srequirements(persona, plans and modes, configurator, env vars, connectors, settings schema and defaults, resources, SDK minimum), so the deploy wizard can stop readingx-stella-*flags.GET /agent-types/sdk-supportreturns the SDK versions this STELLA runs (minSupported,current). -
The build records the SDK an image really has. After each build of an uploaded agent, STELLA reads the installed
stella-ai-agent-sdkversion from the image (newAgentType.sdkVersioncolumn). A build with no SDK, or one below the supported minimum, fails. Deploy, restart and wake refuse an upload whose build is outside the support window. My Agents returnssdkProblemfor those. Uploads built before this have no recorded version and need one rebuild. -
image.commandin the manifest sets a pod's start command. Without it the image's ownCMDruns. -
Agent platform standards (Contributing → Coding standards → Agent platform): the rules that keep STELLA free of agent-specific code, and which module owns which concern.
-
MCP:
platform_settings_getandplatform_settings_updatefor system admins. An assistant can read the platform switches and turn "Review uploaded agents" ...
STELLA Agent SDK 0.10.0
Install with pip install stella-ai-agent-sdk==0.10.0.
STELLA v1.5.0
MCP access and steadier companions. AI assistants such as Claude, ChatGPT and Claude
Code can now connect to a Stella account and work with it: build personas and
plans, set up a session, start an agent and read what was said. It is off until
a system admin switches it on. Error logs no longer keep passwords, keys or
tokens, deploys stop filling the disk, and a companion resuming a long activity
keeps its place. If you upgrade, read "Upgrade notes" first.
Upgrade notes
- Back up the database before you upgrade. This release applies three database migrations on its own during the deploy (access tokens and the MCP audit log, MCP sign-in, and token scopes), and nothing backs up for you first
- MCP is off after the upgrade. Nothing is reachable at
/mcpuntil a system admin switches it on in Settings → Platform Defaults. Sign-in from Claude and ChatGPT uses the existingPUBLIC_API_URLandPUBLIC_FRONTEND_URL, so both must be the addresses the outside world reaches - No manual step and no new required setting. Agent SDK 0.9.0 ships with this release
Added
MCP: AI assistants work with your Stella account
- Stella has an MCP server at
/mcp. An AI assistant connected to it can list, read, create and update personas, plan templates and agent configurations, and read projects, sessions, transcripts and a session's plan state. Nothing can be deleted over MCP. A system admin switches it on or off for the whole platform in Settings → Platform Defaults; while it is off,/mcpand its sign-in pages answer 404 and every token stops working (#772) - Two ways to connect, both in Settings → MCP Access:
- Sign in with Stella: paste the connector address into Claude (claude.ai, Desktop, mobile), ChatGPT or Claude Code. A Stella page opens, you sign in and allow read or read/write access, and the app gets its own tokens. Connected apps are listed there and can be disconnected
- Personal access tokens, for scripts: read or read/write, valid 7 to 365 days, shown once and revocable. They go in the
Authorizationheader only; a token in the address is refused
- Every MCP call is recorded in an audit log (which user, which app, which tool, arguments with secrets removed), kept for 90 days
- An assistant can also run a session from start to end, the way the session view does: create a session, make an invitation link for the participant, deploy an agent with a plan, persona and configuration, follow it and read its log, restart it, stop it, and close the session. Deploying needs read/write access. Env var templates are listed by variable name only, never their values, and agents can't be started in a closed session (#803)
- All 32 tools follow one shape, which the server explains to every assistant when it connects: ids are named after what they point to (
personaId,planId,agentTypeId, …), lists return short summaries and_getthe full object, updates take only the fields to change, and every change returns the result.agent_types_getis new;agent_types_listnow returns summaries instead of every pipeline schema (#817, #806)
Admin settings
- Platform Defaults shows how well the voice fits this machine's hardware: how fast speech is synthesised, and how often sessions had to fall back to sentence-by-sentence playback, at each number of sessions running at once. Each range is coloured green, yellow or red from what was actually measured, and it says when there isn't enough data yet (#765)
Analytics
- Each sentence's synthesis speed (
tts_sentence_speed) and the switch to sentence-by-sentence playback (tts_playback_switch) are now kept as analytics events. Before, they were only in the agent's log, which is deleted when the session ends (#765)
Agent SDK
- Agent SDK 0.9.0 (
pip install stella-ai-agent-sdk==0.9.0). For agent authors: the pipeline publishestts_sentence_speedandtts_playback_switch, andget_chat_history()passes abeforecursor, so an agent can page back through a long history. Details in the SDK changelog
Changed
- Deploys clean up after themselves (
start-k8s.sh). After a healthy rollout, each deploy removes the image generation that has just aged out, so the running image and the one before it stay for rollback, and removes untagged Docker images. The build cache is trimmed towards 50 GB on every deploy, failed ones included, by removing entries older than a week and then older than a day; if it is still bigger, the deploy says so. A warning appears when the image disk is 85% full or more (#780) - A full deploy waits up to 600 s for the backend to become ready (was 180 s), so a deploy whose backend is slow to run its migrations no longer ends red while the backend comes up fine (#790)
Fixed
- Companion mode: an agent resuming a long activity finds when it started even when the start lies far back in the history. Before, it looked only at the last 200 messages and quietly fell back to the whole conversation (#727)
- A goal step ignores tasks left over from when it was flexible or sequential everywhere: in its progress, the plan view, the agent's guidance and where it stores what it collects. The tasks stay saved, so switching back restores them. Before, such a step could stay below 100% (#770)
- Editing a medical or legal expert's verdicts in the Agent Configurator keeps the translated caution line. Before, saving put it back to English only (#722)
- The analytics drill-down no longer breaks when switched between one session and all sessions (#719)
- Publishing the Agent SDK no longer takes GitHub's "Latest release" label from Stella's release (#781)
Security
- Error logs and error responses no longer contain secrets. Tokens in a request's address (an access token sent as
?token=, the sign-in token live updates carry, invitation and public-project links) are masked, and so are passwords, keys and env var values in the body of a request that failed with a server error. Logs written before this upgrade may still contain them (#814, #815)
Known limitations
- Old service images from before this release stay on disk: each deploy now removes one old generation, so the backlog shrinks by one per release. A one-off clean-up is planned (#811), and untagged images left in K3s by moved tags aren't removed yet (#799)
- Over MCP, an agent that has been stopped still shows its last health as
ready(#807), and a session'smessageCountcounts every stored message, not just what was said (#808) - Load balancer or proxy access logs, if your installation keeps them, still record request addresses in full
STELLA Agent SDK 0.9.0
Install with pip install stella-ai-agent-sdk==0.9.0.
Production 1.5.0-19-gb1e12a94
What's Changed
- feat: show how well the voice fits the hardware, under concurrent load, in Platform Defaults (#765) by @DatMoser in #783
- MCP for STELLA: tools, personal access tokens, admin switch, and sign-in for Claude and ChatGPT (#772) by @DatMoser in #786
- MCP sign-in follow-ups from review: refresh scopes, unverified app names, resource test (#772) by @DatMoser in #788
- Bring 1.4.1 back into development: project access checks, version and changelog by @DatMoser in #787
- S5 batch: MCP and steadier companions (1.5.0) by @DatMoser in #796
- fix(ci): keep SDK releases from taking the Latest label by @DatMoser in #791
- fix(configurator): keep translated caution lines when editing a verdict by @DatMoser in #792
- build(frontend): lint with oxlint, and run it in CI by @DatMoser in #793
- fix: page back through history to find a long activity's start tag (#727) by @DatMoser in #794
- fix(deploy): wait up to 600 s for the backend by @DatMoser in #795
- feat: keep only the running image and the one before it, bound the build cache (#780) by @DatMoser in #798
- fix: a goal section ignores its tasks everywhere, not just at the completion gate (#770) by @DatMoser in #800
- feat(mcp): set up sessions and run agents from an AI client (#803) by @DatMoser in #804
- fix(deploy): bound the build cache with --max-used-space alone (#99) by @DatMoser in #810
- fix(mcp): fixes from trying MCP on prod by @DatMoser in #812
- fix(logging): mask tokens in request URLs before logging errors by @DatMoser in #813
- feat(mcp): one shape for every MCP tool by @DatMoser in #816
- chore(release): 1.5.0 changelog and version by @DatMoser in #818
- docs: 1.5.0 — MCP guide and pages that changed by @DatMoser in #819
- docs(mcp): own MCP section with a full tool reference and named scopes by @DatMoser in #821
- release: 1.5.0 by @DatMoser in #822
Full Changelog: v1.4.1...prod/1.5.0-19-gb1e12a94
v1.4.1
A security fix. Upgrade if you run Stella with more than one user account.
Upgrade notes
- No manual step, no new setting and no database migration. The Agent SDK is unchanged (0.8.0)
- System admins follow the same project membership rule as everyone else. To open a project's sessions, be a member of that project
Security
- Access checks tightened: signed-in users can only reach data in projects they belong to