Is it possible to create and share Agent context across my team?
What I want to know is if I setup the context for Katalon AI to think and reply in a specific manner and it should reply the same way to my teammates within same org.
It would be easier to use as a team and get more consistent replies from AI assistant.
You’re asking whether Katalon supports creating and sharing custom AI context (system prompts/behavior instructions) at the organization level so your entire team gets consistent AI responses. Based on my research of current Katalon documentation and features, here’s what’s actually available:
What IS Available for Team-Level AI Configuration
Organization-Level AI Services
Katalon does support organization-wide AI configuration, but it’s limited to AI provider and model selection, not custom context/prompts:
At the organization level, you can configure:
Enable/disable AI features for all team members
Select which AI provider your organization uses (Katalon Default, OpenAI, Azure OpenAI, AWS Bedrock, Gemini)
Set organization-specific API keys that all members use
How to set this up:
Go to Account Settings > System > Configurations > AI Services
Toggle Enable AI Features
Select Organization-Specific AI Key and configure your preferred provider
All team members in that organization will use these settings
You can set up Katalon to reply in a certain way and share this setup with your team. This way, everyone will get similar responses, making it easier for the whole team to work consistently.
Hi! We’re rolling out context and knowledge management soon, but I think from a logical model point of view, sharing (setting up standards) within a project is the first priority since a project encapsulates an atomic unit/team/product that may have distinct standards. But I am sure @huy.tieu will take above-project context into consideration.
“Yes, Katalon supports collaborative AI-driven and agentic testing workflows through shared projects, centralized repositories, reusable test assets, and team-based TestOps management. Teams can share AI-generated test cases, reusable keywords, object repositories, execution history, analytics, and testing context across projects and environments.”
Key ways context is shared across a team include:
Shared TestOps Workspace
Teams can collaborate in centralized TestOps projects where executions, analytics, AI insights, flaky test detection, and quality metrics are accessible to all authorized members.
Reusable AI-Generated Assets
AI-generated test cases, locators, keywords, and objects created in Katalon Studio or TrueTest can be stored in shared repositories for reuse by multiple testers.
Version Control Integration
Integration with Git repositories allows teams to share and synchronize automation scripts, AI-assisted updates, and testing workflows.
Agentic Testing Collaboration
AI agents can use historical execution data, defect trends, and application behavior stored in TestOps to improve future recommendations and autonomous test generation.
Role-Based Access Control (RBAC)
Team administrators can control who can view, edit, approve, or execute shared AI testing resources.
Cross-Team Knowledge Retention
Shared dashboards and analytics help preserve organizational testing knowledge instead of keeping it isolated to individual testers.
Besides the suggestion above, you can also try Configure Agent profile | Katalon Docs in Katalon Studio. This would help your team share the same agent instruction and set up in the same project. Hope that this would help
Hey @akshay_sartabe — Katalon AI just shipped Custom Instructions (the settings persist across conversations, so you don’t have to re-explain context every time). Thought you’d be a good person to try it given how much you push the AI features.
Curious what instructions you’d set up first, and whether it actually saves you time on repeat tasks. Drop your feedback here if you give it a spin
Yes, it is possible to achieve consistent behavior across your team, but not by sharing chat memory between users.
In Katalon Studio, consistency is usually achieved by defining shared project or workspace-level instructions (such as system prompts, rules, or response guidelines). When these are configured at the organization or project level, all team members using the same setup will get responses that follow those defined instructions.
Alternatively, teams can use a shared prompt template or guideline document so everyone interacts with the assistant in the same structured way.