fix(server): stop probing Cursor until enabled - #8175
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This restores Cursor's documented opt-in default, preventing unnecessary cursor-agent probes for untouched installations while preserving explicit opt-ins. The change is isolated to one setting default with focused regression coverage and no schema or deployment impact. You can add or adjust custom eligibility rules. Learn more. |
- Providers no server: compatibilidade preservada após upgrades (pingdotgg#8176), CLIs disponíveis no serviço do macOS (pingdotgg#8173) e fim do probing do Cursor enquanto não estiver habilitado (pingdotgg#8175) - Client-runtime: retry de queries após interrupção de conexão (pingdotgg#8117), com ajustes em authorization/remote e state/runtime - Claude: compactação de threads antigas antes de estourar o uso (pingdotgg#8144), incluindo novo módulo claudeCompaction em packages/shared e medidor de janela de contexto na web - Web: dicas de atalho de thread agora atrasadas em 200 ms (pingdotgg#8172) - Grok: limite nas atualizações cumulativas de saída de ferramentas (pingdotgg#7279) - Mobile: coleta de modelo de dispositivo e versão de SO (pingdotgg#8169) - Docs: release passa a verificar atualizações remotas com migrações de banco (pingdotgg#8177) e doc de providers do Claude atualizada - Conflitos: 2 arquivos conflitaram e foram resolvidos manualmente, mantendo as modificações próprias do fork e incorporando as mudanças do upstream por cima Sync automatico t3code-sync em 2026-08-25T06:05:15-03:00
## What's Changed * feat(mobile): track device models and OS versions by @t3dotgg in pingdotgg/t3code#8169 * fix(grok): bound cumulative tool output updates by @lnieuwenhuis in pingdotgg/t3code#7279 * fix(web): delay thread shortcut hints by 200 ms by @t3dotgg in pingdotgg/t3code#8172 * fix(server): stop probing Cursor until enabled by @t3dotgg in pingdotgg/t3code#8175 * docs(release): verify remote updates with database migrations by @t3dotgg in pingdotgg/t3code#8177 * fix(server): keep provider CLIs available in the macOS service by @t3dotgg in pingdotgg/t3code#8173 * feat(claude): compact old threads before they burn through usage by @t3dotgg in pingdotgg/t3code#8144 * fix(client-runtime): retry queries after connection interruption by @tris203 in pingdotgg/t3code#8117 * fix(server): keep previously used providers working after upgrades by @t3dotgg in pingdotgg/t3code#8176 **Full Changelog**: pingdotgg/t3code@v0.0.34-nightly.20260825.1182...v0.0.34-nightly.20260825.1183 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.34-nightly.20260825.1183
Cursor was turned back on by #7089 after #7459 made optional providers opt-in. Every installation then tried to launch
cursor-agentat startup and during provider health checks, although the installation guide says Cursor is off by default.Restore the Cursor opt-in default and verify that untouched installations skip Cursor probes. Saved Cursor opt-ins still work.
Made by GPT-5.6 Sol through the Codex harness.
Note
Low Risk
Default-only configuration change with regression tests; explicit Cursor opt-in paths are preserved and probing already short-circuits when disabled.
Overview
Cursor is off by default again, matching Grok/OpenCode and the documented install behavior, so fresh or default server settings no longer spawn
cursor-agentduring startup or health checks.The change is in
CursorSettings: the schema decoding default forenabledgoes fromtruetofalse, which flows throughdefaultEnabledForDriverandDEFAULT_SERVER_SETTINGS. Explicit opt-in is unchanged—settings that setproviders.cursor.enabled: true(and matching instance flags) still decode as enabled.Tests were updated to assert the new defaults, cover preserved opt-in, and confirm the provider registry leaves Cursor disabled and does not probe when only other providers are toggled off (without forcing
cursor.enabled: falsein the fixture).Reviewed by Cursor Bugbot for commit d4ab1c7. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Set
CursorSettings.enableddefault tofalseenableddefault inCursorSettingsfromtruetofalseviaSchema.withDecodingDefault(Effect.succeed(false))in settings.ts, so Cursor is off unless the user opts in.providers.cursor.enabled = trueexplicitly.Macroscope summarized d4ab1c7.