Windsurf's banner
Windsurf's profile picture

Windsurf

@windsurf_ai60,892 subscribers

The Windsurf Editor. Tomorrow's Editor, Today. @WindsurfCurrent

Shorts

Introducing Knowledge Base in Wave 8: The ability to import documents from Google Drive for Cascade to use as context. Currently available in beta for Teams!

Introducing Knowledge Base in Wave 8: The ability to import documents from Google Drive for Cascade to use as context. Currently available in beta for Teams!

52,627 Aufrufe

In the near future, developers can expect the Windsurf Browser to do entire tasks for you, powered on context from past actions taken in the browser, IDE, terminal, etc. In its current state, the Browser still is the best way to iterate with websites

In the near future, developers can expect the Windsurf Browser to do entire tasks for you, powered on context from past actions taken in the browser, IDE, terminal, etc. In its current state, the Browser still is the best way to iterate with websites

14,109 Aufrufe

Memories are the previous learnings and context. Developers build up state and context as they do work, which is what makes a more tenured developer more effective than a brand new one with a similar skillset. It would be both inefficient and painful to relearn information from scratch around code structure, architecture, etc each time you needed to do a new task. Memories solve for this. As you do work with Cascade, it can automatically choose to “remember” pieces of information that it learns as Memories, and for any later work, it can choose to pull from this memory bank instead of trying to relearn that information from scratch. You also can manually prompt Cascade to remember parts of conversations as Memories and can manually go in and edit Memories post-fact. Here’s a developer asking Cascade to save some knowledge as a Memory:

Memories are the previous learnings and context. Developers build up state and context as they do work, which is what makes a more tenured developer more effective than a brand new one with a similar skillset. It would be both inefficient and painful to relearn information from scratch around code structure, architecture, etc each time you needed to do a new task. Memories solve for this. As you do work with Cascade, it can automatically choose to “remember” pieces of information that it learns as Memories, and for any later work, it can choose to pull from this memory bank instead of trying to relearn that information from scratch. You also can manually prompt Cascade to remember parts of conversations as Memories and can manually go in and edit Memories post-fact. Here’s a developer asking Cascade to save some knowledge as a Memory:

12,356 Aufrufe

Videos

Keine weiteren Inhalte verfügbar