Commit Graph

34 Commits

Author SHA1 Message Date
CD
c97414cd37 fix(bridge): stall-based approval detection + known issues from deep debugging
- IDLE→stall detection: RUNNING+delta=0 for 6 polls (30s)
- lastModifiedTime-based thinking filter (partial)
- ResolveOutstandingSteps confirmed CANCELS steps (removed)
- HandleCascadeUserInteraction always socket hang up (removed)
- VS Code accept commands: silent success, no effect
- Hybrid approval: focus+all commands sequential, no break
- logToFile: console.log backup added
- Known issues: 4 critical findings documented
- better-antigravity reference added for future research
2026-03-08 14:38:41 +09:00
CD
2574ce6f08 feat: immediate pending detection for all step types 2026-03-08 10:19:27 +09:00
CD
7a38e7ecc9 feat: auto-WAITING detection via stall + step query 2026-03-08 09:56:01 +09:00
CD
0bf3217ae1 fix: panel focus before approval 2026-03-08 09:43:55 +09:00
CD
e7bc4046a4 fix(bridge): hybrid approval — SDK rawRPC + VS Code commands
Root cause: VS Code commands (acceptAgentStep, terminalCommand.run etc)
return undefined silently but don't actually accept WAITING steps.
LS requires HTTPS + CSRF token for RPC calls.

New approach: Phase 1 tries SDK rawRPC (has CSRF auth) with
HandleCascadeUserInteraction + ResolveOutstandingSteps.
Phase 2 tries all VS Code commands as fallback.
All results logged to bridge/extension.log for debugging.

Also removed stall detection (fundamentally broken — stepCount
keeps incrementing from other tool calls during WAITING).
2026-03-08 09:29:40 +09:00
CD
f1f9a0b40b fix(bridge): safer stall detection + VS Code command-based approval
Stall detection fixes:
- Threshold 2→6 polls (30s minimum stall before triggering)
- Added lastModifiedTime tracking (both stepCount AND modTime must freeze)
- Cooldown 30s→60s between pending writes
- Track lastPendingStepCount to prevent retrigger for same stall

Approval handler fixes:
- Replace HandleCascadeUserInteraction RPC with VS Code commands
- Sequential fallback: acceptAgentStep → command.accept → terminalCommand.run
- Same pattern for reject: rejectAgentStep → command.reject → terminalCommand.reject
- Removed SDK dependency check (VS Code commands work without SDK)
2026-03-08 08:14:35 +09:00
CD
9b9c9c71fe fix(bridge): stall-based WAITING detection, remove GetCascadeTrajectorySteps
GetCascadeTrajectorySteps has 775-step hard limit and cannot see
WAITING steps beyond that. No RPC exists for direct WAITING detection.

New approach: if stepCount frozen for 2+ polls (~10s) while status is
RUNNING, treat as WAITING and write pending approval to Discord.
30s cooldown prevents duplicate pending messages.

Also removes the last GetCascadeTrajectorySteps call from Extension -
now only a single GetAllCascadeTrajectories RPC per 5s poll cycle.
2026-03-08 08:05:41 +09:00
CD
f6ae9c87a5 fix(bridge): remove SDK EventMonitor to stop ERR_CONNECTION_REFUSED spam
EventMonitor was dual-polling GetCascadeTrajectorySteps every 2s via rawRPC,
which has a 775-step hard limit and generates connection errors on port change.

Changes:
- Remove entire SDK EventMonitor (onStepCountChanged, onNewConversation, etc.)
- Keep only GetAllCascadeTrajectories POLL at 5s interval
- Remove all sdk.monitor.stop() calls
- Unleash ERR_CONNECTION_REFUSED (127.0.0.1:1080) is Antigravity's own issue
2026-03-08 07:51:50 +09:00
CD
854f33b816 fix(bridge): use GetAllCascadeTrajectories for real-time relay
Root cause: GetCascadeTrajectorySteps has 775-step hard limit,
startStepIndex parameter is completely ignored (verified via direct RPC).

Solution: GetAllCascadeTrajectories returns:
- stepCount: real-time (verified 1413->1457 live)
- latestNotifyUserStep: full notificationContent
- latestTaskBoundaryStep: full taskName/Status/Summary
- stepIndex on each for dedup

E2E verified: Python script -> RPC -> snapshot -> Bot -> Discord
2026-03-08 07:37:39 +09:00
CD
c3964f8e7a fix(bridge): rawRPC direct polling + SDK analysis docs + trial-and-error log
- Root cause: getDiagnostics.lastStepIndex is stale, SDK EventMonitor cannot detect real-time step changes
- Fix: Direct rawRPC('GetCascadeTrajectorySteps') polling every 5s
- Relay: PLANNER_RESPONSE, NOTIFY_USER, TASK_BOUNDARY, WAITING steps
- Added: docs/discord-bridge-analysis.md (full SDK architecture analysis)
- Added: docs/devlog/entries/20260308-003.md (trial-and-error history)
- Added: antigravity-sdk-main/ source reference
- Vikunja: #252 done, #253 created, #251 commented
2026-03-08 07:08:25 +09:00
CD
0c3d6cdb6d fix(bridge): step structure discovery + approval watcher + AI text relay
- plannerResponse.response = user-facing text field (confirmed)
- step.runCommand.commandLine = command (not toolCall.argumentsJson)
- Add response watcher: bridge/response/ → ResolveOutstandingSteps RPC
- Fix AI text: use modifiedResponse/response, last-wins, dedup
- Fix flooding: slice(-delta) to skip old steps on reload
- Bot: 404 cache invalidation for deleted Discord channels
2026-03-08 02:29:17 +09:00
CD
876143d397 fix(bridge): align Extension protocol with Bot — 3 mismatches fixed
- Snapshot: response/chat_snapshot.txt → chat_snapshots/*.json
- Command field: cmd.message → cmd.text (matches Bot.write_command)
- RPC: GetConversation (404) → GetCascadeTrajectorySteps
- Bundle sql-wasm.js + sql-wasm.wasm into VSIX (45KB→379KB)
- Handle consumed flag, clean 38 stale commands
- Add extractAIText helper with fallback chain
2026-03-08 01:14:20 +09:00
CD
4bb72921ae feat: embed antigravity-sdk source — zero npm dependencies (45KB VSIX) 2026-03-08 00:45:07 +09:00
CD
bc2fca0da4 feat: complete SDK rewrite — antigravity-sdk v1.6.0 integration (1155→280 lines) 2026-03-08 00:38:45 +09:00
CD
8c0736fe2b probe: Trial E2 — Electron webContents + undocumented VS Code commands 2026-03-07 23:38:25 +09:00
CD
87094e00b0 feat: subscribeToStream on new cascade — real-time StreamCascadeReactiveUpdates subscription 2026-03-07 23:23:16 +09:00
CD
12131b9103 probe: Trial D3 — streaming RPC with protocol_version=1 + cascadeId combined 2026-03-07 23:05:54 +09:00
CD
4d1bb7a443 probe: Trial D2 — fixed protobuf encoding (protocol_version=1, cascadeId, ConnectRPC framing) 2026-03-07 22:58:56 +09:00
CD
2794a26c77 probe: Trial D — streaming RPCs + JSON retry with live auth context 2026-03-07 22:52:30 +09:00
CD
d213c2f0f5 probe: Trial B2 — getChromeDevtoolsMcpUrl, getWsTargets, remote-debugging-port scan 2026-03-07 21:22:23 +09:00
CD
7ba1e1b977 probe: Trial A (extension exports) + Trial B (chat commands) — systematic approach 2026-03-07 20:52:33 +09:00
CD
0d90b257c3 feat: extractFromLogs for AI response text, remove failed RPCs, summary fallback 2026-03-07 20:31:58 +09:00
CD
b0c2f865c8 feat: try LoadTrajectory + multiple RPCs for actual AI response text, summary as fallback 2026-03-07 20:15:27 +09:00
CD
7415ab7890 feat: immediately relay summary when new conversation detected with AI response 2026-03-07 20:06:19 +09:00
CD
41f90b3b15 fix: track ALL trajectories, detect new conversations, summary fallback per-traj 2026-03-07 19:55:34 +09:00
CD
0c9664542e fix: use getDiagnostics for cascade IDs + summary fallback + stop poll spam 2026-03-07 19:43:31 +09:00
CD
dfc76a9b4b fix: fallback chain for step retrieval (5 method+field combos) 2026-03-07 19:32:32 +09:00
CD
b6adeff402 fix: use real API response (trajectoryId, current:true, step count diffing) 2026-03-07 19:25:48 +09:00
CD
be6fae71de fix: correct RPC method names from LS binary (Heartbeat, GetUserTrajectoryDescriptions, GetCascadeTrajectorySteps) 2026-03-07 19:00:11 +09:00
CD
f2ed431aa5 fix: LS ConnectRPC use HTTPS when detected, not port heuristic 2026-03-07 18:31:13 +09:00
CD
91b3a7ef20 feat: LS ConnectRPC bridge for AI response relay to Discord 2026-03-07 18:15:01 +09:00
CD
67619e8950 docs: mid-session devlog + entry 002 (sendPromptToAgentPanel discovery) 2026-03-07 17:39:00 +09:00
CD
2a4ef8d0d9 fix: extension fs.watch accepts all event types + debounce (Windows compatibility) 2026-03-07 14:00:08 +09:00
CD
52fed8c1d3 feat(phase3): VS Code Extension 스캐폴드 - bridge 연동 (approve/reject/text relay) 2026-03-07 11:32:30 +09:00