Only re-sync WeChat session provider after a failed Cursor attempt.
Memind CI / Test, build, and release guards (push) Successful in 5m24s
Memind CI / Test, build, and release guards (push) Successful in 5m24s
Avoids double applySessionLlmProvider on normal Goose chat paths that blocked fast release. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
+5
-1
@@ -2961,7 +2961,9 @@ export function createWechatMpService({
|
||||
intentKind: wechatIntent.kind,
|
||||
policy: wechatCursorPolicy,
|
||||
});
|
||||
let wechatCursorAttempted = false;
|
||||
if (useWechatCursorChannel) {
|
||||
wechatCursorAttempted = true;
|
||||
try {
|
||||
reply = await executeWechatCursorAgentRun({
|
||||
agentRunGateway,
|
||||
@@ -3001,7 +3003,9 @@ export function createWechatMpService({
|
||||
}
|
||||
}
|
||||
if (!reply) {
|
||||
await ensureSessionProvider(sessionId, user.userId, { intentKind: wechatIntent.kind });
|
||||
if (wechatCursorAttempted) {
|
||||
await ensureSessionProvider(sessionId, user.userId, { intentKind: wechatIntent.kind });
|
||||
}
|
||||
reply = await executeSessionReply(
|
||||
(pathname, init) => fetchForSession(sessionId, pathname, init),
|
||||
sessionId,
|
||||
|
||||
Reference in New Issue
Block a user