AI assistant
Find code and tests in project context
Search across folders with a local index that reuses files already analyzed.
In this guide
Before you start · PremiumExample: where is the total calculated?Search for the function and open the resultRecognize the text you are editingResult and next stepBefore you start · Premium#
This guide covers tools included in Code Weaver Premium. Sign in to your account in the IDE and check that Premium is active. Without Premium you can still browse, search, edit and save your files.
Example: where is the total calculated?#
Before changing calculateTotal, you want to find the function and related tests, even when the frontend and API live in different folders. Project context searches associated folders, with or without Git, and opens each result in the correct file.
Search for the function and open the result#
Search also refreshes the index, reusing unchanged files. Search for part of a path or text when you do not know the function name.
- From chat, open Conversation tools → Project context.
- Choose Refresh index. The summary shows the files, symbols, imports and test files found.
- Enter calculateTotal in Search project context. Leave Result type set to All and choose Search.
- Open a match to reach its file and line in the editor. To narrow the search, choose Symbol, Test or another result type.
Recognize the text you are editing#
Current buffer marks a result from text open in the editor. Buffers are used for that search; the persistent index represents saved files. This lets you find a newly renamed function before saving.
Under Related tests, open one of the suggested paths. Read the test to check that it covers the behavior you want to change.
Result and next step#
You have located the source and possible tests without searching folder by folder. Agents can query the same index through authorized IDE tools. Return to chat, attach useful files with @ and describe the change, or run the relevant test from the Tests panel.