Xenition is an AI workspace with 23 real editing surfaces — document, spreadsheet, slides, code, diagram, video studio, 3D and more — that all share one memory. A single chat can write a document, design a deck, build and deploy a full-stack app, render a video or reconcile a pile of invoices, and hand the result to a surface you can edit.

Yes. The free plan includes 25,000 credits a month and needs no credit card. Paid plans start at about $16.67 per month billed yearly, with usage-based credits shared across every surface.

What if the tool I need is not in Xenition?

Ask for it in the product chat. The team reviews every request and most ship within 3 to 7 days.

How is Xenition different from a chatbot with plugins?

A chatbot returns text. Xenition returns work on a surface you can keep editing, and remembers it. It also does things a single-surface tool structurally cannot: learning paths with decaying mastery that can refuse to teach a topic whose foundation has lapsed, invoice reconciliation where confidence comes from arithmetic rather than a model's self-assessment, explainer videos where narration is measured before any frame is cut, and meeting notes that expand your own typed notes and drop any action item that cannot quote its source line.

Can Xenition build and deploy a real application?

Yes. Describe an app and Xenition generates a working product with a real Postgres database, authentication, storage, an API, a web front end and a native mobile app, then deploys it. There are also 153 full-stack templates, each with a live demo.

Which apps does Xenition connect to?

121 apps including Slack, Gmail, Google Calendar, Google Drive, Notion, GitHub, Linear, Jira, HubSpot, Salesforce, Stripe, QuickBooks and Airtable. Agents can act in them, with an approval gate on anything destructive.

Is Xenition available outside the browser?

Yes — a desktop app for macOS, Windows and Linux with a global hotkey and silent auto-updates, plus native mobile apps for iOS and Android. The interface is available in 36 languages.

All connectors

GitHub integration

GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features

Connect GitHub to Xenition and work with it from chat, from an agent, or on a schedule — alongside every other app you have connected, in one workspace.

What you can do with GitHub

Ask in plain language and Xenition calls the right one:

Abort Repository Migration — Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
Accept a repository invitation — Accepts a PENDING repository invitation that has been issued to the authenticated user.
Add app access restrictions — Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps must be installed on the repository with 'contents' write permissions.
Add assignees to an issue — Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
Add a repository collaborator — Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add email for auth user — Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add field to user project — Tool to add a custom field to a user-owned GitHub Projects V2 project. Use when you need to add fields like status, priority, or custom data to organize project items.
Add item to user project — Tool to add an issue or pull request to a user-owned GitHub project. Use when you need to add existing repository items to a project board.
Add labels to an issue — Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Add org runner labels — Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
Add or update team membership for a user — Adds a GitHub user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.
Add or update team project permissions — Adds a classic project to a team or updates the team's permission on it. This endpoint grants or updates permissions for a team on a specific classic project (not Projects V2). The authenticated user must have admin permissions for the project. Both the team and project must belong to the same organization. Requirements: - The project must be a classic project (not GitHub Projects V2) - The authen
Add or update team repository permissions — Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Add project collaborator — Adds a specified GitHub user as a collaborator to an existing organization project with a given permission level. Note: This endpoint is for organization projects (classic). You must be an organization owner or a project admin to add a collaborator. Classic projects are being deprecated in favor of the new Projects experience.
Add a repository to an app installation — Adds a repository to a GitHub App installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Add repo to org secret with selected access — Adds a repository to an existing organization-level GitHub Actions secret that is configured for 'selected' repository access.
Add selected repo to org secret — Grants an existing repository access to an existing organization-level Dependabot secret when the secret's visibility is set to 'selected'; the repository must belong to the organization, and the call succeeds without change if access already exists.
Add runner labels — Adds and appends custom labels to a self-hosted repository runner, which must be registered and active.
Add selected repository to an organization secret — Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
Add selected repository to an organization variable — Grants a repository access to an organization-level GitHub Actions variable, if that variable's visibility is set to 'selected_repositories'.
Add a selected repository to a user secret — Grants a specified repository access to an authenticated user's existing Codespaces secret, enabling Codespaces created for that repository to use the secret.
Add social accounts for the authenticated user — Adds one or more social media links (which must be valid, full URLs for platforms supported by GitHub) to the authenticated user's public GitHub profile.
Add status check contexts — Adds status check contexts to a protected branch's required status checks. This action appends new status check contexts to the existing list of required status checks for a protected branch. The branch must already have branch protection enabled with status checks configured. Note: The 'contexts' parameter is deprecated by GitHub in favor of 'checks' array. For new implementations, consider using
Add sub-issue to an issue — Tool to add a sub-issue to a parent GitHub issue using GraphQL. Use when you need to establish a parent-child relationship between issues. Requires the 'sub_issues' GraphQL feature to be enabled.
Add team access restrictions — Adds teams to the list of teams with push access to a protected branch. This action grants additional teams push access to a protected branch. Unlike 'Set team access restrictions' (PUT), this action adds to the existing list rather than replacing it entirely. Prerequisites: - The repository must be owned by an organization (not a personal account) - The branch must have protection rules enabled -
Add users to codespaces access for an organization — Adds organization members to the list of users granted Codespaces access billed to the organization. IMPORTANT: This endpoint requires the organization's Codespaces billing access to be set to 'selected_members' mode. If not already configured, use the GITHUB_MANAGE_ACCESS_CONTROL_FOR_ORGANIZATION_CODESPACES action first to set visibility to 'selected_members'.
Add user access restrictions — Adds users to the list of people allowed to push to a protected branch in an organization repository. Important notes: - This action only works on organization-owned repositories (not personal repos) - The branch must already have protection rules with restrictions enabled - Users must have write access to the repository to be added - The combined total of users, apps, and teams is limited to 100
Get GitHub API root — Retrieves a map of all top-level GitHub REST API resource URLs and their templates.
Approve a workflow run for a fork pull request — Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Assign an organization role to a team — Assigns an existing organization-level role (identified by `role_id`) to a team (identified by `team_slug`) within a GitHub organization (`org`), provided the organization, team, and role already exist.

…and 20 more GitHub actions available in the workspace.

Give an agent access to GitHub

An agent you create can use GitHub on your behalf and keep working while you do something else. Every action an agent takes goes through an approval gate first, so nothing touches your GitHub account without you agreeing to it.

Other connectors

Frequently asked questions

How do I connect GitHub to Xenition?

Open the connectors directory in Xenition, find GitHub, and sign in when the authorisation window opens. The connection is managed for you — there is no API key to create, paste or rotate.

What can Xenition do with GitHub?

Xenition can run 50 different GitHub actions, including Abort Repository Migration, Accept a repository invitation, Add app access restrictions. You ask in plain language and the right one is called for you.

Can an agent use GitHub on my behalf?

Yes. Agents can use GitHub while you do something else, and every action passes through an approval gate before it runs.

Is there a free plan?

Yes. Xenition starts free with 25,000 credits a month and no credit card, and all connectors are available on every plan.