Migrating from lf assist

The lf assist command — an interactive agent session built on the OpenCode runtime — has been removed. This page explains what changed and where to go instead.

What changed

• lf assist is gone. There is no replacement subcommand; running lf assist now prints an "unknown command" error.
• Bare lf opens the interactive shell again. Running lf with no subcommand opens an interactive shell — a scrollable command transcript with a persistent input, history, Tab completion, and a fuzzy command palette over every CLI command.
• The OpenCode integration is fully removed — the plugin bridge (libs/adapters/opencode), .opencode/opencode.json generation, and the @opencode-ai/plugin dependency are gone. Nothing in this codebase spawns the opencode binary anymore.

If you used lf assist for exploration

Use the interactive shell instead — type a command name directly, or open the fuzzy palette with Ctrl+K and pick from live suggestions, the same discovery workflow assist offered, without a model in the loop:

lf
# type a command and press Enter, or Ctrl+K to search

Every command still enforces its own --confirm/safety gates exactly as it would from a plain shell invocation.

If you used lf assist for agent-driven workflows

Use the MCP server integration (apps/mcp-server) instead. It exposes LenserFight's lens, battle, and workflow operations as MCP tools that any MCP-capable agent client (Claude Code, Claude Desktop, and others) can call directly — the same command surface assist wrapped, without an extra CLI-spawning layer in between.

Related

• Operate LenserFight from the interactive shell
• CLI Getting Started
• MCP Server Setup