mirror of https://github.com/lobehub/lobehub.git synced 2026-09-20 04:56:13 +08:00

Files

T

History

Arvin Xu 230b8037f1 🐛 fix(hetero): stop settling a run whose output ingest discarded as success (#19658 )

* 🐛 fix(hetero): stop settling a run whose output ingest discarded as success

A device/sandbox hetero run can finish with every one of its events thrown
away and still be recorded as a clean turn: the user is left on the `...`
assistant placeholder forever, with no error, no retry affordance, and the
topic/task retired as answered.

`heteroIngest` has two paths that discard a whole batch and answer 200 — the
operation row is no longer `running`, and the topic's `runningOperation`
marker no longer names this operation. The producer reads 200 as delivery, so
`BatchIngester.drain()` succeeds, `exitedClean` is true, and `heteroFinish`
receives `result: 'success'` for a run that persisted nothing.

Observed on a real run: the CLI did all the work (16 steps, opened the PR it
was asked for, $5.31 of tokens) while the server stored one `stream_start` and
then silently dropped the rest.

Three changes, so the loss is reported wherever it can be:

- `heteroIngest` returns `{ accepted, reason }` and stamps the first refusal
  on the operation row. A refusal is permanent, so it is an ack, not a
  transport error the producer should retry.
- `BatchIngester` fails the stream on a refusal instead of retrying, which
  surfaces at `drain()` and makes the run finish as an error carrying why.
- `heteroFinish` reads the row marker back and downgrades a `success` receipt
  to a failure, covering producers that predate the ack contract.

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

* 🐛 fix(hetero): let terminal-operation callbacks reach the refusal path

`authorizeOperationCallback` rejects an operation-token callback with CONFLICT
as soon as its row is terminal, so `heteroIngest` never reached the refusal it
was just taught to report: the ingester spent its whole retry budget on a
permanent failure, no rejection marker was recorded, and `heteroFinish` was
turned away by the same guard — leaving the turn on its unresolved placeholder.

`hetero:ingest` and `hetero:finish` now opt into `allowTerminalOperation`. The
allowance is per call site, never implied by the capability, so token renewal
(which also asks for `hetero:ingest`), goal mutations and `model:invoke` stay
strict. Every other check still runs, and neither callback gains any write
power: the service refuses them on the same terminal status, which is precisely
the answer they exist to deliver. It also aligns the narrow token with the
user-session producers, which skip this guard entirely today.

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

---------

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

2026-09-18 23:30:05 +08:00

e2e

…

man/man1

✨ feat(cli): add lh doctor to diagnose the whole chain in one command (#19626 )

2026-09-18 02:00:18 +08:00

scripts

🐛 fix(cli): keep workspace packages inside the embedded CLI bundle (#19391 )

2026-09-10 18:21:46 +08:00

src

🐛 fix(hetero): stop settling a run whose output ingest discarded as success (#19658 )

2026-09-18 23:30:05 +08:00

tests

✨ feat(cli): record local hetero agent runs as execution snapshots (#18874 )

2026-08-31 01:51:19 +08:00

.npmrc

👷 build: migrate workspace to pnpm 12 (#19324 )

2026-09-09 19:43:11 +08:00

package.json

🔖 chore(cli): bump version to 0.0.55 (#19618 )

2026-09-16 09:23:11 +08:00

pnpm-workspace.yaml

🐛 fix(portal): guide outside-workspace HTML publishing (#19338 )

2026-09-11 15:58:31 +08:00

README.md

…

tsconfig.json

…

tsdown.config.test.ts

🐛 fix(cli): keep workspace packages inside the embedded CLI bundle (#19391 )

2026-09-10 18:21:46 +08:00

tsdown.config.ts

🐛 fix(cli): keep workspace packages inside the embedded CLI bundle (#19391 )

2026-09-10 18:21:46 +08:00

vitest.config.mts

👷 build: migrate the test suite to vitest 5 (#19355 )

2026-09-10 22:18:49 +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>