LiveContext Files

What is new

Cursor joins the CLI agents

Run agents on your own Cursor plan. The Cursor CLI now ships in the bridge image, next to Claude Code, Codex, Gemini CLI and Mistral Vibe.

• Sign in once: docker exec -it -e NO_OPEN_BROWSER=1 livecontext-bridge cursor-agent login (open the link it prints), or set CURSOR_API_KEY in your .env. Then check it in Settings > AI Providers > CLI > Cursor > Verify Connection.
• Eight models: Auto, Composer 2.5, Claude Opus 5.5, Claude Sonnet 5, GPT-5.5, GPT-5.6 Sol, Gemini 3.1 Pro, Grok 4.7. A free Cursor plan runs Auto only; the other models need a paid Cursor plan, and the app says so if you pick one.
• Access: admin only by default, like the other CLIs (Settings > AI Providers > CLI > Cursor > Who can use this bridge).
• Good to know: Cursor cuts a single tool call after 60 seconds, reports token usage once a run ends, and has no reasoning-effort setting (the effort is part of the model).

Fixed: CLI agents get their platform tools again

In a Docker install, an agent running on a CLI (Claude Code, Codex, Gemini CLI, Mistral Vibe, Cursor) started without any LiveContext tool: no workflows, tables, files or integrations. It answered from the model alone, and the run still showed as successful. The bridge now proves which user and workspace each run belongs to, and the tools are back. Nothing to configure: update both images.

AI Providers settings, regrouped

API Keys, CLI (one toggle per CLI) and Models. Links to the old per-CLI tabs keep working.

Also new

• The home page shows your workspace at a glance, with an Agents block.
• Tables: search and filters cover the whole table, exports contain what they say, and a table or column edit that fails is no longer shown as saved.
• Credentials: connections that use your own OAuth app are told apart, and the Google bring-your-own-key guide covers test users and API enablement.
• The workflow builder keeps a tool input named like a call field (name, type, action...).

Upgrading

docker compose pull && docker compose up -d. Database migrations run on their own. The bridge image is about 270 MB larger (the Cursor CLI).

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

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

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

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

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

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

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