feat(devin-desktop): rename Windsurf→Devin Desktop + fix(continue) thread-safe adapter#2410
Merged
Conversation
Cognition rebranded Windsurf to Devin Desktop (June 2026); Cascade is EOL July 1. Rename the (unreleased) windsurf integration to devin-desktop before first publish: - Package hindsight-windsurf -> hindsight-devin-desktop (module hindsight_devin_desktop, CLI hindsight-devin-desktop, DevinDesktopConfig, bank default 'devin-desktop', HINDSIGHT_DEVIN_DESKTOP_BANK_ID) - Rule now writes to .devin/rules/hindsight.md (preferred path) instead of the legacy .windsurf/rules/; trigger: always_on unchanged - MCP config path stays ~/.codeium/windsurf/mcp_config.json (Devin Desktop's on-disk data dir, unchanged by the rebrand) - Official Devin logo; docs + integrations.json + README refreshed with the 'formerly Windsurf' framing - Registries updated: test.yml job, release-integration.sh, generate_changelog, integrations.json (strict JSON), docs page 26 unit tests + gated live-MCP E2E pass; ruff check+format clean; real-app smoke against local Hindsight verified (init writes both files; live recall returns seeded facts). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…afe) The adapter runs on a ThreadingHTTPServer (one worker thread per request) but shared a single Hindsight client across all of them. The client's aiohttp session is bound to the thread/event-loop that first used it, so the first @hindsight recall worked and every one after threw 'Timeout context manager should be used inside a task' — Continue then showed an error context item and the model answered with no memory. Resolve the client per request (test-injected clients still used as-is), and close per-request clients in a finally so the fresh aiohttp session doesn't leak a connector each call. Bump to 0.1.1. Found via a real in-editor VS Code test. Adds a regression test asserting per-request client resolution across the threaded server. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
34891d4 to
af8f8a3
Compare
Member
|
Reviewed — the code looks good, and none of the red CI is from this diff (it touches only integrations + docs +
On the actual changes:
No code changes needed here. Recommend merging #2427 first, then a re-run. One sequencing note: #2417 defers a doc note until this lands, so #2410 should merge before #2417. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR bundles two things (per request, kept in one PR):
1. Rename Windsurf → Devin Desktop
Cognition rebranded Windsurf to Devin Desktop (June 2026); Cascade is EOL July 1. Since
hindsight-windsurfwas merged but never published, renamed it todevin-desktopbefore first release.hindsight-windsurf→hindsight-devin-desktop(module, CLI,DevinDesktopConfig, bankdevin-desktop,HINDSIGHT_DEVIN_DESKTOP_BANK_ID).devin/rules/hindsight.md(preferred path); MCP config stays~/.codeium/windsurf/mcp_config.json(Devin's data dir, unchanged by rebrand)integrations.json+ README refreshed; all registries updated2. fix(continue): resolve a fresh Hindsight client per request
Found via a real in-editor VS Code test. The Continue adapter runs on a
ThreadingHTTPServer(one thread per request) but shared a single Hindsight client. The client's aiohttp session is thread/loop-bound, so the first@hindsightrecall worked and every one after threwTimeout context manager should be used inside a task— Continue then showed an error context item and the model answered with no memory.finallyso the fresh aiohttp session doesn't leak a connector each callhindsight-continue→ 0.1.1 (the published 0.1.0 has this bug)Verified live: 5 recalls in a row all succeed; 0 timeout errors; 0 unclosed-connector warnings. 17 continue tests pass; ruff clean.
🤖 Generated with Claude Code