Settings → Knowledge
Knowledge lives in a sidebar group under Settings → Knowledge, split into three tabs. Opening Settings → Knowledge lands you on the Assistant tab.Assistant tab
Knowledge used by the AI Chat Assistant and during test creation.Project Summary
An AI-generated summary of your website’s functionality and structure, created by analyzing your pages and user interactions. The summary is always part of chat context and updates as your site evolves. What’s Included:- Overview of your platform’s purpose and main functionality
- Key features and user flows
- Important pages and their purposes
- Integration points and external services
Navigate to Knowledge Settings
Navigate to Settings →
Knowledge.
The summary requires initial site analysis to be completed. If no summary
appears, ensure you’ve run some tests or site analysis first.
Assistant Rules
Rules the chat assistant always follows when answering questions and creating tests. See Rules below.PR Review Rules
Rules applied during PR review. See Rules below.Library
Link and text knowledge items that AI assistants can reference when generating tests and answering questions. Library items are stored at the project level and shared across all team members. What You Can Add:- URLs: Link to documentation sites, help pages, API docs. URLs are crawled and indexed.
- Text Content: Add custom instructions, project notes, or guidelines. Text items are stored and summarized.
Memories
Knowledge items the assistant creates automatically from your conversations, capturing useful facts it learns as you work. You can review, edit, and delete memories from the Assistant tab so the assistant keeps an accurate picture of your project.Test Agent tab
Knowledge used by the test agent during test execution.Agent Rules
Rules the test agent follows while executing tests. Agent Rules support targeting filters - by application, labels, scenario, or URL path - so a rule applies only to matching tests instead of every test in the project. See Rules below.Agent Visuals
Image uploads that help the agent visually identify UI elements during execution. Add screenshots of buttons, icons, or layouts the agent should recognize so it can act on them reliably.Crawling tab
Manage crawling sessions, your project domains (suggested domains and excluded paths), and the Reset Knowledge Graph action. See Crawling Sessions for how crawling builds the agent’s understanding of your application.Rules
Rules are how you give the AI persistent instructions that should always apply. There are three kinds, each used at a different stage:- Assistant Rules - followed by the chat assistant during chat and test creation.
- PR Review Rules - applied during PR review.
- Agent Rules - followed by the test agent during test execution. Agent Rules support targeting filters (by application, labels, scenario, or URL path) so a rule applies only to matching tests.
| Use Case | Example | What It Achieves |
|---|---|---|
| Domain knowledge | ”This is a railway booking system for American routes. Stations use AMTRAK codes.” | Agent understands domain terminology |
| Quality standards | ”Tests should fail if obvious typos or broken layouts are detected.” | Agent enforces quality expectations |
| Data requirements | ”When creating test users, always use Swedish names and addresses.” | Agent generates appropriate test data |
| UI conventions | ”Red buttons indicate destructive actions - verify confirmation dialogs appear before clicking.” | Agent handles UI patterns correctly |
| Auth flows | ”Login requires SMS 2FA. The code will be available in the test inbox.” | Agent knows to check inbox for 2FA |
| Timing expectations | ”Page loads may take up to 10 seconds in staging. Wait for loading indicators to disappear.” | Agent waits appropriately |
| Known limitations | ”The checkout flow is broken on mobile viewports - skip mobile tests for checkout.” | Agent avoids known issues |
- Keep rules concise but specific - Agent Rules are consulted on every relevant action.
- Focus on guidance that applies broadly; use Agent Rule targeting filters when something should apply only to certain tests.
- Include domain-specific terminology and behaviors.
- Mention any unusual UI patterns or interactions.
- Update rules when your product behavior changes.
- Test-specific instructions - put these in test steps instead
- Credentials - use Configs instead
- URLs - use Applications and Environments instead
- Temporary workarounds - document in test steps where needed
How Knowledge Works
Knowledge has different roles during test creation versus test execution:| Knowledge Type | Test Creation (Chat) | Test Execution |
|---|---|---|
| Library (link/text items) | Used - searched semantically | Not used (unless attached to the test) |
| Memories | Used | Not used (unless attached to the test) |
| Knowledge Graph | Used - site structure + semantic search | Not used |
| Project Summary | Used | Used (via agent context) |
| Assistant Rules | Used | Not used |
| Agent Rules | Not used | Used - every relevant decision (subject to targeting filters) |
| Agent Visuals | Not used | Used |
| Chat file uploads (attachments) | Used in that chat only | Not used |
- The assistant searches your knowledge on demand - semantic search across your Library, Memories, and the site/feature knowledge graph - rather than stuffing everything into the prompt.
- The Project Summary provides overall context about your application.
- Assistant Rules shape how the assistant answers and what tests it proposes.
- The AI generates test steps based on all the above context.
- Knowledge items explicitly attached to the test (text and memory items only; links are excluded as too large)
- Agent Visuals
- Agent Rules matching that test (subject to targeting filters)
- The Project Summary
This separation means you can safely update knowledge without affecting tests
that are already running or scheduled.
Attaching Knowledge to a Specific Test
Library and Memory items aren’t used during execution by default. To give the agent a specific item as context while a test runs, attach the knowledge item to that test case. This is the supported way to make a Library or Memory item available during execution (text and memory items only; links are excluded as too large).Project Knowledge vs. Chat-Local Files
Understanding the scope of your knowledge helps you organize it effectively: Project Knowledge (Settings → Knowledge):- Shared across all chats in the project
- Accessible to all team members
- Permanent and searchable by semantic search
- Best for: Official documentation, stable specifications, product rules
- Per-message attachments scoped to a single conversation
- Other users’ chats cannot access them
- Not persisted as project knowledge - they do not automatically become reusable Library items
- Best for: Experimental specs, PR descriptions, feature branch docs, exploratory work
Knowledge Graph & Semantic Search
Crawled documentation and indexed knowledge are stored in a Knowledge Graph with embeddings that enable semantic search - finding relevant information based on meaning rather than exact keywords. During chat and test creation, the assistant searches your knowledge automatically and on demand:- Analyzes your request to understand intent
- Searches your Library, Memories, and the site/feature knowledge graph for semantically similar content
- Provides the most relevant information to the AI assistant
- Uses clear titles to improve search accuracy
Adding Library Items
Navigate to Knowledge Settings
Navigate to Settings →
Knowledge and open
the Assistant tab.
Fill in Details
Fill in the title and content for your knowledge item. Use clear,
descriptive titles that reflect the content - this helps both the AI search
and allows you to reference specific knowledge by name in chat (e.g., “use
the API documentation knowledge”).
Organization Tips
- Use Clear Titles: Make Library items easy to find with specific, descriptive names
- Keep Content Current: Regularly review and update documentation links
- Remove Outdated Info: Delete or update knowledge that no longer reflects your product
- Test Your Knowledge: Ask the chat assistant questions to verify it finds the right information
- Avoid Contradictions: When updating specs, remove old versions to prevent confusion
Troubleshooting
Knowledge not being found in chat:- Ensure content has been fully processed (check status indicators)
- Try different search terms or questions
- Verify the content is relevant to your question
- Use clear, descriptive titles for better semantic search results
- Check that you’ve saved the rule on the correct tab (Assistant Rules, PR Review Rules, or Agent Rules)
- For Agent Rules, verify the rule’s targeting filters (application, labels, scenario, URL path) actually match the test you’re running
- Review test results to see whether the rule’s guidance is being followed
- Ensure you’ve completed initial site analysis
- Try running a few tests to build the knowledge graph
- Manually refresh the summary after adding new functionality
- Remember: files attached in chat are conversation-specific
- To share with team, add the content to the Library instead
- Other team members need to attach it to their own chats, or use project knowledge