mirror of https://github.com/lobehub/lobe-chat.git synced 2026-06-14 03:30:19 +00:00

Files

T

History

Arvin Xu 61586b9377 🐛 fix(agent): persist & deliver image attachments for device/sandbox hetero runs (#15685 )

* 🐛 fix(agent): persist file attachments in hetero early-exit user message

The hetero-agent early exit in execAgent created the user message without
the `files` relation, so attachments sent from the SPA gateway path
(executionTarget=device / sandbox) were never linked via messagesFiles and
disappeared once the optimistic client message was replaced by the server
snapshot. Attach the deduped `fileIds` the same way sendMessageInServer
does on the local-mode path.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* ✨ feat(agent): deliver image attachments to device/sandbox hetero runs

Persisting the messagesFiles relation fixed display, but the dispatched
CLI still never saw the image — local mode feeds the persisted imageList
into sendPrompt for vision, while the device/sandbox dispatch protocols
(agent_run_request / sandbox runner) only carried a text prompt.

- resolve attached images into signed URLs in the hetero early exit
  (metadata-only, non-fatal) and carry them through heteroParams
- add imageList to the agent_run_request wire type and dispatchAgentRun
  params (gateway client + server service)
- extract buildHeteroExecStdinPayload into @lobechat/heterogeneous-agents
  so the three dispatch sites (desktop spawnLhHeteroExec, lh connect
  daemon, server sandbox runner) build the same content-block payload:
  systemContext, prompt, then image blocks
- lh hetero exec already coerces image blocks via coerceJsonPrompt and
  normalizeImage (url → base64 for Claude Code, materialized path for
  Codex), so no CLI consumer changes are needed

openclaw/hermes (runHeteroTask) keep text-only prompts — their dispatch
goes through a separate one-shot tool protocol.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* ♻️ refactor(heterogeneous-agents): move exec stdin wire contract to a pure /protocol entry

The server sandbox runner imported `buildHeteroExecStdinPayload` through the
`/spawn` barrel, which (with no `sideEffects` hint) bundles the whole spawn
machinery into the Next.js server chunk. Its `process.cwd()`-rooted dynamic
fs calls then make Vercel's output file tracing glob the entire repo source
tree into every serverless function (+~69 MB each), pushing the 4 largest
functions past the 250 MB uncompressed limit and failing the deployment.

Split the dispatch wire contract (stdin payload builder + content-block
types) into a new pure, isomorphic `/protocol` export and point all three
dispatch sites (server sandbox runner, desktop main, `lh connect` daemon) at
it. `/spawn` re-exports the moved symbols so executor-side callers are
unaffected. Also declare `sideEffects: false` for the package.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-12 00:02:51 +08:00

e2e

chore: remove LOBE-XXX markers from code comments (#15422 )

2026-06-03 17:02:24 +08:00

man/man1

🐛 fix(cli): handle agent_run_request in lh connect so device dispatch doesn't time out (#15634 )

2026-06-10 15:19:01 +08:00

src

🐛 fix(agent): persist & deliver image attachments for device/sandbox hetero runs (#15685 )

2026-06-12 00:02:51 +08:00

.npmrc

⏪ revert: revert pnpm v11 migration (#14372 )

2026-05-01 14:45:28 +08:00

package.json

Update dependency node to v24.16.0 (#14621 )

2026-06-11 09:24:21 +08:00

pnpm-workspace.yaml

✨ feat(verify): Agent Run delivery checker system (#15489 )

2026-06-08 09:16:35 +08:00

README.md

feat: add unified messaging tool for cross-platform communication (#13296 )

2026-03-31 00:26:32 +08:00

tsconfig.json

🐛 fix(cli): preserve content/state for connect local file/shell tools (#15442 )

2026-06-04 01:28:11 +08:00

tsdown.config.ts

🐛 fix: fix minify cli (#13888 )

2026-04-16 18:39:18 +08:00

vitest.config.mts

🐛 fix(cli): preserve content/state for connect local file/shell tools (#15442 )

2026-06-04 01:28:11 +08:00

README.md

@lobehub/cli

LobeHub command-line interface.

Local Development

Task	Command
Run in dev mode	`bun run dev -- <command>`
Build the CLI	`bun run build`
Link `lh`/`lobe`/`lobehub` into your shell	`bun run cli:link`
Remove the global link	`bun run cli:unlink`

bun run build only generates dist/index.js.
To make lh available in your shell, run bun run cli:link.
After linking, if your shell still cannot find lh, run rehash in zsh.

Custom Server URL

By default the CLI connects to https://app.lobehub.com. To point it at a different server (e.g. a local instance):

Method	Command	Persistence
Environment variable	`LOBEHUB_SERVER=http://localhost:4000 bun run dev -- <command>`	Current command only
Login flag	`lh login --server http://localhost:4000`	Saved to `~/.lobehub/settings.json`

Priority: LOBEHUB_SERVER env var > settings.json > default official URL.

Shell Completion

Install completion for a linked CLI

Shell	Command
`zsh`	`source <(lh completion zsh)`
`bash`	`source <(lh completion bash)`

Use completion during local development

Shell	Command
`zsh`	`source <(bun src/index.ts completion zsh)`
`bash`	`source <(bun src/index.ts completion bash)`

Completion is context-aware. For example, lh agent <Tab> shows agent subcommands instead of top-level commands.
If you update completion logic locally, re-run the corresponding source <(...) command to reload it in the current shell session.
Completion only registers shell functions. It does not install the lh binary by itself.

Quick Check

which lh
lh --help
lh agent <TAB>