@agentvault/muse-bridge 0.1.20 → 0.1.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +22 -0
- package/dist/index.d.ts +4 -0
- package/dist/index.js +4389 -1703
- package/dist/muse-driver.d.ts +5 -0
- package/dist/muse-provider.d.ts +13 -0
- package/dist/muse-session.d.ts +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -45,3 +45,25 @@ pruned cache path.
|
|
|
45
45
|
`--yolo` only when both Access grants are on (`workAllowed` and `gatesRemoved`).
|
|
46
46
|
Otherwise `--disable-shell` and `--disable-write` (no terminal, no file-tool
|
|
47
47
|
writes).
|
|
48
|
+
|
|
49
|
+
## Meta reasoning recovery
|
|
50
|
+
|
|
51
|
+
Every native Meta Muse turn uses a temporary loopback adapter pinned to Meta's
|
|
52
|
+
Responses API. It removes opaque reasoning from older settled turns while
|
|
53
|
+
preserving conversation messages, tool calls/results, settings, and the existing
|
|
54
|
+
Muse session. Reasoning in the current tool loop stays until Meta rejects that
|
|
55
|
+
request with the specific encrypted reasoning expiry error. The adapter then
|
|
56
|
+
retries that provider request once with its remaining reasoning removed; Muse and
|
|
57
|
+
its tools are not restarted or replayed. Successful SSE responses stream through.
|
|
58
|
+
Opaque requests using `previous_response_id` pass through without rewriting.
|
|
59
|
+
|
|
60
|
+
Removed reasoning cannot contribute its previous private reasoning continuity;
|
|
61
|
+
the conversation and tool history remain available. The adapter neither edits
|
|
62
|
+
Muse journals nor rotates session IDs. It binds only to loopback with a fresh
|
|
63
|
+
secret route and closes at turn end. Diagnostics contain counts and fixed outcomes.
|
|
64
|
+
|
|
65
|
+
If an eligible room or owner-attested DM turn fails before attempting a reply,
|
|
66
|
+
the bridge attempts one generic failure notice on that turn's captured reply
|
|
67
|
+
channel. The notice waits at most ten seconds before the next queued turn advances.
|
|
68
|
+
Echo exec/provider behavior remains unchanged; eligible terminal failure notices
|
|
69
|
+
apply to both providers.
|
package/dist/index.d.ts
CHANGED
|
@@ -1,10 +1,13 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
|
+
import { type HistoryRecoveryCommandInput } from "@agentvault/agentvault";
|
|
2
3
|
import { type BridgeConfig } from "./config.js";
|
|
3
4
|
import { MuseSession } from "./muse-session.js";
|
|
4
5
|
import { MuseDriver, type MuseSpawnFn } from "./muse-driver.js";
|
|
5
6
|
import { type RoomMcpServer } from "./muse-room-http.js";
|
|
6
7
|
import { type LifecycleChannel, type RoomChannel } from "./bridge.js";
|
|
7
8
|
import type { ServiceBackend } from "./service/backend.js";
|
|
9
|
+
type HistoryRecoveryRunner = (input: HistoryRecoveryCommandInput) => Promise<void>;
|
|
10
|
+
export declare function maybeRunRecoverySubcommand(argv?: string[], env?: NodeJS.ProcessEnv, runRecovery?: HistoryRecoveryRunner): Promise<boolean>;
|
|
8
11
|
export type BootChannel = RoomChannel & LifecycleChannel & {
|
|
9
12
|
start(): Promise<void>;
|
|
10
13
|
stop(): Promise<void>;
|
|
@@ -35,4 +38,5 @@ export interface MainHandle {
|
|
|
35
38
|
shuttingDown: () => boolean;
|
|
36
39
|
}
|
|
37
40
|
export declare function main(opts?: MainOpts): Promise<MainHandle | undefined>;
|
|
41
|
+
export {};
|
|
38
42
|
//# sourceMappingURL=index.d.ts.map
|