LiveContext Files

What is new

License 1.1

• The Community Edition is now published under the LiveContext Sustainable Use License 1.1. Using, self-hosting and modifying LiveContext for your own business is unchanged.
• Agencies can still host and run LiveContext for their clients: one deployment per client, as part of the services they provide to that client (setup, workflows, integrations, training, maintenance or support).
• Selling LiveContext hosting to customers generally (hosting plans anyone can order, one-click or marketplace deployments run for the customer) needs a commercial license. Publishing a template people deploy on their own servers does not.
• Plain-language answers are in LICENSING.md. Earlier releases keep the license they shipped with.

Workflows and agents

• Agents attach notes to the node they explain. The canvas places each note beside its node and shows it when you focus that node, in the editor or on a run.
• Notes an agent writes without a colour alternate through the palette.
• Switching the layout direction places attached notes beside their node again.
• A plan saved with set_plan never stores a node the plan parser would skip.

Runs

• Hovering an epoch in the canvas run timeline opens its card: outcome, start, end and duration. The Analysis duration and cost chart shows the same card, and node labels in an epoch comparison are clickable.
• Pausing, unpinning, cancelling or deleting a failing workflow ends its "still failing" reminders.

App

• Every search, filter, sort, tab, page number and view mode is kept in the address, so a reload or a shared link reopens the page as you left it.
• The chat card for a sensitive action names what will run and why it asks, with the full details one click away.
• The model picker also offers the models an admin has hidden, last, under a "Hidden models" heading.
• Tables: progress cells show their caption, read-only cells stay read-only, a refused edit gives the stored value back, and row notifications are translated.
• The two-factor reminder is shown only to the owner of the active team workspace.

Security

• The bridge authenticates every call with a per-install secret the app generates on first boot.
• Stored credentials move to an authenticated encryption envelope; existing rows are re-encrypted at startup.
• Access tokens are bound to this install and to a live login session: signing out or changing your password withdraws them. Tokens issued before the update keep working until they expire, so nobody is signed out by the upgrade.
• CORS answers only this install's own origins (APP_PUBLIC_URL, APP_BASE_URL). Set CORS_ALLOWED_ORIGINS if your frontend is served from another domain.
• Security headers and a nonce-based Content Security Policy on the app; interfaces render in an isolated frame.
• Outbound requests follow a single egress policy and are pinned to the address that was checked. Self-hosted installs can still reach their local network.
• Browser-agent callbacks may only target the app.
• The third-party images of the compose file (Postgres, Redis, MinIO, SearXNG) are pinned by digest.

Upgrading

• Run git pull before docker compose pull: the compose file adds a volume for the bridge secret and pins image digests.
• Database migrations run automatically on start.

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.3.6
• ghcr.io/livecontext-ai/livecontext-ce-frontend:v0.3.6
• ghcr.io/livecontext-ai/livecontext-ce-bridge:v0.3.6

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

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

• docker.io/livecontext/livecontext-ce-frontend:v0.3.6
• docker.io/livecontext/livecontext-ce-bridge:v0.3.6

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

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

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

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