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

Linear integration

Linear is a streamlined issue tracking and project planning tool for modern teams, featuring fast workflows, keyboard shortcuts, and GitHub integrations

Connect Linear 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 Linear

Ask in plain language and Xenition calls the right one:

Archive issue — Archives an existing Linear issue by its ID, removing it from active views while preserving its data for future reference. Use this action when you need to remove an issue from active work without permanently deleting it — for example, when an issue is no longer relevant, was created by mistake, or has been superseded by another issue. Archiving is reversible via the unarchive mutation, unlike per
Archive Project — Archives an existing Linear project by its UUID, removing it from active views. Use this action when you need to mark a completed or obsolete project as archived. Archiving is reversible (projects can be unarchived later), but confirm the project name with the user before executing, especially in bulk operations.
Archive Project Update — Archives a project update in Linear, hiding it from the default view while preserving its data. Use this action when you need to clean up old or obsolete project status updates without permanently deleting them. Archived updates can be unarchived later if needed. This action is irreversible only in the sense that the project update will be hidden from active views until explicitly unarchived.
Create attachment — Creates a new attachment and associates it with a specific, existing Linear issue.
Add reaction to comment — Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.
Create a comment — Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing.
Create linear issue — Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. All UUID parameters (state_id, assignee_id, cycle_id, label_ids, project_id) must belong to the same team as team_id. The created issue's id is returned in data.id — capture it for use as parent_id in sub-issues
Create issue relation — Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues.
Create a label — Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned. Both new and existing labels return the same object structure; check the label's `createdAt` or compare IDs to determine if creation occurred.
Create Project — Creates a new Linear project with specified name and team associations.
Create Project Milestone — Tool to create a project milestone in Linear with a name and optional target date and sort order. Use when you need to add milestones to track progress within a project.
Create Project Update — Tool to create a project status update post for a Linear project. Use when you need to post progress updates, status reports, or announcements for a project.
Create Team — Creates a new team in Linear with the specified name and key. Use this action when you need to create a new organizational unit or work group in a Linear workspace. Teams are fundamental organizational structures in Linear that group issues, projects, and members together. Once created, the team's key becomes the prefix for all issues created within that team (e.g., 'ENG-123'). IMPORTANT: The key
Delete issue — Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent. Archiving is permanent with no built-in undo — confirm the issue identifier and title with the user before executing, especially in bulk operations.
Get all teams (Deprecated) — DEPRECATED: Use ListLinearTeams instead (returns paginated payloads with members and projects); this tool returns simpler id/name-level data for all teams visible to the connected workspace with no server-side filtering. Match teams on stable team id, not display name, as names are not guaranteed unique. Partial results reflect workspace permission scope, not tool failure. Skip this call if team_i
Download issue attachments — Downloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension.
Get a comment — Retrieves a single Linear comment by its unique ID. Returns comprehensive details including the comment body, author, timestamps, associated issue, and thread information. Use this action when you need to fetch details about a specific comment, such as when displaying comment information, checking comment status, or retrieving comment content for processing. The comment ID can be obtained from iss
Get current user — Gets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may be a bot or service account rather than a human user. Use the returned `id` field (nested under `data.viewer`) for downstream Linear operations requiring user ID filtering. To search or compare other workspace members, use LINEAR_LIST_LINEAR_USERS instead.
Get cycles by team ID — Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints). Results are team-scoped to the given team_id. To identify the active cycle, check that the current date (in UTC) falls between a cycle's startAt and endAt fields; either field may be null. Results may be paginated — follow page_info cursors to retrieve all cycles.
Get create issue default params — Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.
Get Linear issue — Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.comments.nodes for comment IDs), subscribers, and due date. Does not include parent, milestone, cycle, or relation graphs—use LINEAR_RUN_QUERY_OR_MUTATION for those. Optional fields (labels, proje
Get Linear project — Retrieves a single Linear project by its unique identifier. Use when verifying a newly created or updated project, or when fetching detailed project information by ID.
Get Project Update — Retrieves a specific project update by its unique identifier. Use when you need to fetch details about a specific project status update, including the update content, health status, timestamps, and associated project information. This action is useful when verifying a newly created project update or retrieving historical project update information.
List comments — Lists comments from Linear workspace accessible to the authenticated user. Use this action when you need to retrieve comments for analysis, reporting, or tracking discussions across issues. The response includes comment content, timestamps, author information, and associated issue details. Supports pagination for large result sets.
List issues by team ID — Tool to list all issues for a specific Linear team, scoped by team ID. Use when you need to retrieve issues belonging to a particular team without fetching workspace-wide issues. This is more efficient than workspace-wide listing followed by client-side filtering.
List issue drafts — Tool to list issue drafts. Use when you need to fetch draft issues for review or further editing. Check `pageInfo.hasNextPage` in the response to determine if additional drafts exist beyond the current page.
Get all cycles — Retrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied. In large multi-team workspaces this produces heavy responses — filter client-side by team ID and date range using each cycle's startsAt/endsAt fields. Cycles are team-scoped; always group by team ID to avoid mixing sprints across teams. To identify the active sprint, verify the current UTC tim
List Linear issues — Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned. Can filter by assignee_id. Only project_id and assignee_id server-side filters are supported; label, state, team, cycle, or date filters must be done client-side or via LINEAR_RUN_QUERY_OR_MUTATION. Response is a flat issues array plus page_info object (not GraphQL nodes/pageInfo). F
Get labels — Retrieves labels from Linear. If team_id is provided, returns labels for that specific team; if omitted, returns all labels across the workspace. Label names are not unique across teams — always use returned IDs, not names, and track each label ID with its team ID. In large workspaces, results may paginate; follow pageInfo.hasNextPage and pageInfo.endCursor to retrieve all labels.
List linear projects — Retrieves all projects from the Linear account. Returns a flat array (not a GraphQL connection) with fields id and name; use LINEAR_RUN_QUERY_OR_MUTATION for progress, state, issues, or team linkage. No server-side filtering: all workspace projects are returned regardless of team or name — filter client-side. Multiple projects can share identical names; always confirm project_id before downstream

…and 17 more Linear actions available in the workspace.

Give an agent access to Linear

An agent you create can use Linear 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 Linear account without you agreeing to it.

Other connectors

Frequently asked questions

How do I connect Linear to Xenition?

Open the connectors directory in Xenition, find Linear, 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 Linear?

Xenition can run 47 different Linear actions, including Archive issue, Archive Project, Archive Project Update. You ask in plain language and the right one is called for you.

Can an agent use Linear on my behalf?

Yes. Agents can use Linear 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.