Integrations bring OneWorld to you, so you do not have to change the way you work. Your team keeps using the tools it already has, and OneWorld connects to them.
A connected repository lets an agent work against your real code instead of a description of it, and it lets a session carry the link back to what the work was based on. The more of your tools are connected, the more the next person can pick up without asking anyone.
What integrations are for
Integrations are how the tools your team already works in become part of your company memory.
Every department has one place where its real work happens. Engineering has the repository and the pull request behind a change. Product has the spec and the decision behind a launch. Marketing has the brief and the numbers behind a campaign. Legal has the contract and what was flagged in review. Support has the ticket and what has already been tried.
An integration brings that place into OneWorld, so the reasoning around the work arrives with it. A teammate who opens the session later sees what it was based on, without opening five tabs or asking the person who did it.
- A decision gets questioned three months later. The session holds the reasoning and the connected tool holds what it produced, so nobody reconstructs it from memory.
- The person who did the work has moved on. Their session and everything it links to are still there, so the next person continues from the work instead of from a handover call.
- Two teams start the same investigation weeks apart. The earlier session and the change it led to are already in the memory, so the second team begins where the first one stopped.
- Someone joins mid-project. They read the work and follow the links back to the code, the ticket, or the document it came from, rather than booking time with four people.
- An agent needs to act, not only answer. With the repository connected, it works against your real code, and what it changes stays attached to the session that asked for it.
The pattern is the same in any department, any company, and any industry. Wherever your work already happens, connecting that place is what lets the next person continue it rather than rebuild it.
Connect GitHub
An organization admin connects GitHub. The steps are in Quickstart.
What GitHub can do
The GitHub App is installed on the repositories your teams use. Repository activity sync needs repository access plus Metadata: read, Contents: read, Pull requests: read, and Issues: read.
Actions that create or update issues, pull requests, files, or commit statuses need the matching write permissions in GitHub.
OneWorld checks the GitHub App's installed permissions before it calls GitHub.
If a teammate cannot open an integrated item, ask an admin to confirm their permissions in OneWorld and in the connected tool.
How the GitHub token is stored is on Security.
Ask
In Ask, the agent explores and answers. It does not edit files, run commands, or commit.
Adding another tool
OneWorld is built to fit the way your team already works, so the set of integrations grows with what your team needs. If a tool you rely on is not connected yet, tell your organization owner or your OneWorld contact which tool it is, the workflow it supports, and who needs it. We will work with you to connect it.