Skip to content

LiveContext CE v0.2.8

Choose a tag to compare

View all tags
@livecontext-ai livecontext-ai released this 02 Aug 00:51
· 5 commits to main since this release
v0.2.8
746f573

What is new

Workflow builder

  • The node palette and the run history now live in the side panel. The canvas keeps the
    space; both are one click away instead of covering what you are editing.
  • Run-mode trigger picker, pinnable from the canvas toolbar. Choose which trigger a manual
    run fires without leaving the canvas, and pin the one you keep using.
  • Loop-back edges, n8n style. An edge can now point back at an earlier node without a
    dedicated While hub, so iteration reads the way you draw it.
  • Sub-workflow nodes no longer show the referenced workflow's name, which went stale as soon as
    the target was renamed.

Agents

  • An agent can stop a run - including the one it is executing inside, which previously had
    no way to end itself.

Marketplace

  • CE-exclusive publications, badged as such and blocked on managed cloud.

Fixes

  • The execution engine no longer resets an epoch while an async agent is mid-delivery, which
    could drop that agent's result.
  • Chained workflow triggers fire again; the same lazy-proxy dispatch bug that broke them also
    affected the sub-workflow and error-trigger lanes, now resolved through one path.
  • Loop iteration caps are enforced consistently across replicas.
  • interface-client's default HTTP client had no read timeout at all: a single unresponsive
    interface call could hang a worker indefinitely. It is now bounded.
  • The workflow builder stops accepting parameter aliases that no creator ever read, so a typo
    fails loudly instead of being silently ignored.

Self-hosted release notifications

Your install learns about a new release from a public feed on the cloud. That feed used to be
updated by hand as part of a cloud deployment, and it silently fell behind for months - installs
were told they were current when they were not. It is now written by the release itself, after
its smoke-test passes, so a published release and an announced release cannot diverge.

Nothing changes in how you update: the in-app banner links to the release notes, and updating is
still docker compose pull then up -d.

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.8

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

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

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

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

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

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

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

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

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

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

  • quay.io/livecontext/livecontext-ce-screenshot-renderer:v0.2.8 (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.

Assets 2
Loading