Docs
Tools, integrations, and engines
How Gwen can use connected tools, business systems, browsers, files, code workspaces, and execution engines without exposing the plumbing.
What can Gwen connect to?
Gwen can connect to communication, productivity, storage, CRM, finance, research, developer, and automation systems when a mission needs access.
What are engines?
Engines are internal execution options Gwen can route to when the work requires special capability, such as research, drafting, coding, browsing, document processing, or runtime execution.
Does the user need to choose the engine?
The user should ask for the outcome. Gwen should decide whether the work needs a normal model call, a tool connection, a browser path, a code runtime, or another capability.
What requires connection or approval?
Read-only planning may proceed with available context. Sending, posting, purchasing, changing records, pushing code, deploying, or destructive operations should require the right connection and approval.