release: v2.0.5 - Telegram Business Reporting & Core Resilience
This commit is contained in:
@@ -1276,6 +1276,11 @@ export class SidebarChatProvider implements vscode.WebviewViewProvider, BridgeIn
|
||||
context: this._context,
|
||||
ai,
|
||||
defaultModel: cfg.defaultModel || 'gemma4:e2b',
|
||||
// Hand the dispatcher a thunk into ConnectAI's action-tag
|
||||
// executor so specialist outputs like `<create_file>` actually
|
||||
// hit disk. Without this, agents would *claim* to create
|
||||
// files while nothing happened — the exact bug we just fixed.
|
||||
executeActionTags: (text) => this._agent.executeActionTagsOnText(text),
|
||||
onEvent: emit,
|
||||
});
|
||||
} catch (e: any) {
|
||||
@@ -1285,6 +1290,13 @@ export class SidebarChatProvider implements vscode.WebviewViewProvider, BridgeIn
|
||||
value: `1인 기업 모드 실행 실패: ${e?.message ?? e}`,
|
||||
});
|
||||
} finally {
|
||||
// The webview's send button is locked into the "generating" state
|
||||
// when the user submits; it only unlocks on `streamEnd`. The
|
||||
// normal chat path posts that from inside AgentExecutor, but
|
||||
// the company turn never touches AgentExecutor, so we have to
|
||||
// post it ourselves here — otherwise the input stays disabled
|
||||
// with the red Stop button after the round completes.
|
||||
this._view?.webview.postMessage({ type: 'streamEnd' });
|
||||
void this._sendReadyStatus();
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user