LiveContext CE v0.2.13

What is new

What is new

Integrations: the catalog roughly doubles

• 278 new integrations across five waves, and 13,500 more endpoints. The catalog now authors 978 APIs and 32,466 endpoints, against roughly 700 and 19,000 at the last release. The waves were built by a committed generator rather than by hand, which is what made the scale survivable: it converts a vendor-published spec into the catalog's own format, and it is now the durable asset, not the batch it produced.

• Where those integrations reach your install depends on the cloud link. An install linked to the cloud receives them through the signed catalog bundle, which upserts them one API at a time. An install that has never linked boots from the catalog snapshot shipped inside the image, and that snapshot predates these waves, so it stays on the previous set until it links.

• The generator's own defects were the interesting part. Eight converter faults were found that produce a file which imports green and is dead on arrival: an endpoint with an empty output schema projects an empty object over a perfectly good HTTP 200, so nothing errors and nothing arrives. Each was fixed at the converter, not in the file it emitted.

• A duplicate check that compared names could silently overwrite an existing API. Matching on a fuzzy name and a base URL host, wave 1 replaced three integrations that were already in the catalog. The import is now gated by a preflight that compares the payload key by key at every depth, and that gate runs in CI.

• An integration whose domain no longer exists was withdrawn. Trieve is gone rather than shipped as a call that cannot resolve.

• A provider that refuses the call is reported as a failure. It used to be able to come back as a success with nothing in it, which is the same shape as a call that worked and returned little.

• A binary answer is never dropped because the schema forgot to name it. Any endpoint that replies with bytes, an image, a sound, a document, now hands them back whatever its declared output schema says.

Generation

• A history of every generated asset, and regeneration from an asset's own recipe. What produced an image is kept with it, so making a variant does not mean reconstructing the parameters by hand. The history reads as a slice rather than loading everything.

• The dialog asks for a provider, then a model. That is the order the decision is actually made in, and the dialog is warmed so the list is there when it opens. Each provider is marked, a model that takes files says what each input is and how many it accepts, and a model inherits the values the catalogue already knows instead of asking for them again.

• A parameter whose values come from the provider now loads them. A source that answers with an array was unreachable, so a model's languages never arrived and the field stayed empty with no error to show for it.

• One odd catalogue response no longer takes the page down.

Model catalog

• Models are discovered from each provider's own /models endpoint. The curated table stays the authority on what a model costs and how hard it may be called; discovery keeps the list current without waiting for a release.

• A discovered model is priced like any other feed row, from OpenRouter, rather than arriving with no price at all.

• No model is left uncapped. Rate limiting hands control back to the curated table, and the models seeded by migration get a ceiling too.

• The sync no longer deletes tiered-priced models. Every Chinese model with per-tier pricing was being removed on each run; the current flagships are curated rows now.

Chat

• A tool call waits on its permission card instead of ending the turn. Answering the card resumes the same call, so a grant no longer means asking again from the top. A Stop beats a late approval on every way a park can end, and the hold is capped below the shortest CLI wait so the bridge cannot time out underneath it.

• The Connect card stays put for a rule the user already granted.

• The composer draws its merged actions with the app's own menu, and a narrow composer no longer cuts off its own send button.

Workflows

• Choose which account a catalog step runs on, at run time. A step that talks to a provider you hold several keys for no longer has to be duplicated per account. The selector is set from the inspector with a settings-style toggle, and the account names are discoverable to agents.

• Pin a version without having run it first. Pinning used to require an existing run to point at; it now mints the production run itself.

• A rerun of an automatic run asks first. Restarting one is not something to discover after the fact.

• A sub_workflow call waits for the child epoch to close instead of publishing a prefix of it.

• Folders on workflows, agents, tables, pages and applications. Each list keeps its own preview faces and its own ordering, the folder is in the URL, and Back walks out of a folder rather than off the page. Creating something inside one leaves it there.

• A workflow page stops asking the same question five times.

Credentials

• Rename a credential. Every workflow pin is by numeric id, so renaming moves nothing under a running workflow. Two renames are refused on purpose, and each says why: one over a credential matched by its name rather than by an integration, and one that would collide on the owning workspace.

• A credential's NAME can no longer answer for another provider. A key named after one service was being handed to another because the name matched. That is fixed at the resolver.

Applications and marketplace

• App previews are muted by default, with a sound toggle beside the star, on the marketplace cards and in the app's own settings cog.

• Every Explore refinement is answered in SQL, and the grid is paged. Filtering a window that had been chosen by a different criterion is not filtering, which is why a newly published app could be unreachable past the first 50 rows.

• Editable copy is opted into at install.

Files, video and the rest

• The two errors production was actually serving on file bytes are fixed, a 500 and a 401 on the same route, from two unrelated causes.

• generateVideo clips carry page-scored audio, muxed in by the renderer.

• Schedule notifications open on the Triggers tab.

Self-hosting

• A fork of this repository renders its own landing page correctly. The export was deleting the landing screenshots on the grounds that a self-hosted install never serves that page, which is true only for a build that resolves to the ce edition. A build from source with no edition set resolves to cloud, renders the page, and asked for two images that were no longer there. A release gate now refuses to publish a tree that is missing any asset its own frontend requests.

Update an existing install

git pull
docker compose pull
docker compose up -d

The compose file pins this release's image tag, so run git pull first. Your data lives in Docker volumes and is kept across updates.

Fresh install

git clone https://github.com/livecontext-ai/livecontext-ce
cd livecontext-ce
docker compose up -d

Then open http://localhost:3000

Images

Pull from whichever registry you prefer, the digests are identical.

• ghcr.io/livecontext-ai/livecontext-ce:v0.2.13

• ghcr.io/livecontext-ai/livecontext-ce-frontend:v0.2.13

• ghcr.io/livecontext-ai/livecontext-ce-bridge:v0.2.13

• ghcr.io/livecontext-ai/livecontext-ce-screenshot-renderer:v0.2.13 (opt-in renderer profile)

• docker.io/livecontext/livecontext-ce:v0.2.13

• docker.io/livecontext/livecontext-ce-frontend:v0.2.13

• docker.io/livecontext/livecontext-ce-bridge:v0.2.13

• docker.io/livecontext/livecontext-ce-screenshot-renderer:v0.2.13 (opt-in renderer profile)

• quay.io/livecontext/livecontext-ce:v0.2.13

• quay.io/livecontext/livecontext-ce-frontend:v0.2.13

• quay.io/livecontext/livecontext-ce-bridge:v0.2.13

• quay.io/livecontext/livecontext-ce-screenshot-renderer:v0.2.13 (opt-in renderer profile)

Each image is also tagged v0.2, v0 and latest if you prefer to track a moving line rather than pin an exact release.