Skip to content

LiveContext CE v0.2.10

Choose a tag to compare

View all tags
@livecontext-ai livecontext-ai released this 03 Aug 03:58
· 3 commits to main since this release
v0.2.10
f9c1a26

What is new

What is new

Workflow runs

  • The run you pick is the run you keep. Picking a run in the run history bound the canvas to it but left the address bar on the run the page had been opened with. A refresh therefore took you back to the previous run, and the run you were reading could be neither shared nor bookmarked. The address bar now follows your pick, still without reloading the page, and the browser's Back button behaves: coming from the editor returns to the editor, switching between runs does not fill your history with them.

  • A run opens on all of its epochs. Opening a run landed on its most recent epoch, hiding every other fire behind a selector nobody had touched. The cumulative view is the default again on the canvas, in the Run panel and in the workflow page's Application tab, and both the run bar and the application's epoch control say "All epochs" in words instead of a number that read like an epoch. Picking one epoch still sticks across surfaces, and so does going back to all of them. A published application, where the app itself is what you came for, still opens on its newest run.

  • The run history shows the real execution time. The duration column measured an epoch's whole lifetime, idle tail included, so a workflow whose executions take seconds reported hours (32h42m for a run of a few seconds). It now measures from the first node start to the last node end, and a wait inside the graph still counts because the waiting node's own row spans it. The same wrong figure was reaching the epoch timeline, the Application tab, the agent fire result and macro report, and the public app and showcase payloads; all of them now read the corrected value.

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

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

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

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

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

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

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

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

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

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

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

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