Kosmodrom

Lists repository branches with sha, default/protected flags and the task key from each name (taskKey); search filters by a name substring. With taskID, only that task's live branches are listed, plus suggestedName - the live branch or the server-convention name for a new one (a task has one live branch). Creates nothing.

Creates a bug when the user asks to log a defect and publishes it right away: with an approver it goes to approval, otherwise to work to the assignee. Placement is one of: a feature (featureID or featureKey), a version (versionID) or the product backlog (productID); type is the criticality (the nature of the defect is the separate bugType field), and bugs always have a testing stage. Stage assignees: employee uuid, "any" (any employee) or null (no such stage; the work stage always exists). Returns the key, link, status and allowed transitions.

Deletes a chat message. Irreversible: the token owner can delete their own message within 60 minutes, chat administrators and the product lead any message. Intended for an explicit user request to remove an unneeded message (duplicate, wrong chat).

Edits the token owner's own regular message within 60 minutes of sending: text replaces the old one, mentions are recalculated from mention tokens, passed attachments replace the old ones ([] removes all). The chat shows an "edited" mark; later corrections go as a new message, quoting the original only when other messages already follow it.

Returns messages addressed to the token owner (direct chat, mention, reply to their message) still without their answer, regardless of age: chat and link, why it is addressed, the related item, the message with attachments. Useful when the user asks what awaits their reply; pages continue with nextCursor while hasMore.

Adds or removes the token owner's reaction to a chat message - a textless reply. Only Kosmodrom web reactions are available (meanings in reaction); an existing reaction is not added twice, system messages take no reactions, and message reactions are keyed by who added them.

Returns chat messages from a cursor, oldest to newest; without a cursor - the latest ones. hasMore tells whether more messages exist in the requested direction; an after cursor returns newer messages, such as replies to a sent one. A task chat without messages yet returns an empty page. Each attachment has attachToken, which can be inserted into a spec / result as is. chatType is the chat type: direct for a direct chat, entity for the chat of a task, bug, feature or product (entityType), group for the rest; quotes and mentions follow it.

Sends a message on behalf of the token owner to a chat (a task's chat ID is the task ID) or, with userID, a direct message to an employee; replyMessageID quotes a message that other messages already follow. Intended for blocking questions, replies to messages addressed to the token owner and messages the user asks for - not for status updates, summaries or links to created items. Messages newer than the last read (the after cursor) may already hold the same question or its answer. Returns chatID, the message and an after cursor; the message can be edited or deleted within 60 minutes.

Creates a product component (without componentID; productID and title are required) or updates a component's name and description, or removes its main Figma frame; omitted fields stay unchanged, module membership is not affected. Only at the user's request or with their consent: the product structure belongs to the team.

Returns the workspace's conventions and description template for a new feature, task or bug (content) and the template revision (rulesRevision) that creation requests carry. For a task, the template depends on its work type.

Converts an amount between RUB, USD, EUR and CNY at the Bank of Russia rate for a date: non-business days use the last business day's rate, cross rates go via RUB, dates after tomorrow are rejected. Returns rate (units of to per 1 from) and result (the amount in to, 2 decimals).

Replies in a Figma comment thread through the company's integration, visible to everyone with access to the file; the server adds an "employee and agent" signature. Source: url or designID; commentID - the thread or a reply in it. Suitable when a remark is fixed or the answer is unambiguous; disputed points are left to the user.

Returns Figma design comments through the company's integration: threads with author, date, text, replies and pinned node. Source: url (a frame or page returns threads inside it, a file - all) or designID of an imported design; author.isIntegration marks replies already sent via Kosmodrom. A later reply may cancel a remark; the Figma API cannot mark threads resolved.

Imports Figma frames into a task, bug or feature through the company's Figma integration, like pasting a design in the web app (snapshot, layers, assets): one entity, up to 10 frame links with node-id per request, large frames 2-3 per request to stay within client timeouts (after a timeout the import keeps running on the server; the entity's designs, by nodeID with ":" such as 12:34, show what was imported within 1-2 minutes); a failed frame does not stop the others. Per frame returns status (imported, updated, unchanged, linked - linked but not refreshed, error), designID and a designToken marker, or error with action - how to fix it; the designToken in an entity's spec or result holds the link to the design, and the same marker in another entity of the product links it there on save. moduleID / componentID (product:structure privilege) set the module's or component's main frame (one frame, no marker); re-import refreshes the snapshot and keeps markers.

Returns a feature's code: its tasks, the product's repositories, live branches and commits by task keys. Useful for checking a feature's spec against the implementation.

Returns a feature by ID or key (#F12): spec, gist, plan tasks (tasks, top to bottom by ord) and bugs as compact lines, employees (users), designs and attachments (attaches) with file IDs, and specRevision - the spec revision needed to edit the spec. Useful when the user asks about a feature, its plan or who works on it (workAssigneeID).

Creates a feature in a product version when the user asks to add one; it is visible to the team at once, with no approval step. The server creates no tasks for it: per the feature creation template, a design task follows when the modules need design, other tasks only at the user's request. Returns the feature's link, product, version, ord and specRevision.

Deletes a feature with all its tasks and bugs (soft cascading deletion, no restore). Irreversible; only at the user's explicit request. Returns deletedTasks, the number of tasks and bugs deleted.

Lists the features of a product or one version in the web order (ord ascending), for an overview of what a product contains. spec and specRevision come only with includeSpec (much larger response), completed features only with allowDone; the next page is requested with nextCursor and the same parameters.

Searches a product's features by meaning in title, gist and spec, with word forms, AI aliases and typo tolerance in titles - e.g. when the user asks to find a feature or where new work belongs. Returns short entries with an excerpt and score; the next page uses the last item's cursor with the same query and filters.

Returns the context for updating a feature's spec from its tasks: feature.spec, tasks[].spec and tasks[].result in one batch plus the workspace's spec-update guidelines (instructions); writes nothing. includeTaskIDs adds full contexts with chats of tasks with discrepancies. mode=analyze - differences and a full new version without saving; mode=apply - when the user asks to apply the update.

Updates a feature's title, spec, gist, version (moves it), analyst or position (ord) at the user's request; only passed fields change. Changes shared team data; feature status transitions remain a human decision, not available here. Returns the link, product, version, ord, specRevision and changed fields.

Returns a person's queue in a product (the token owner's or userID's), grouped by the stages where they are the assignee of the current stage: approval, work, review, testing. Within a group a task already in progress (state work) comes first, then urgent bugs, urgent tasks, bugs and tasks. includePool adds pool - the shared "any" pool for work, review and testing matched to the person's role and level; in the token owner's own queue it lists only tasks they can take. Useful when the user asks what to work on next.

Returns a file's content by fid: an image as an image, text as text, up to 5242880 bytes; larger files, video, archives and other binaries are not returned inline. A design file ID that is no longer found was replaced by a re-import; the entity's current designs have the new one. Access follows the items the file is attached to, or the token owner's own upload. An attach token without an entry in attaches means the attachment was deleted or the text copied.

Uploads a file for attachment: attachToken goes into a task, bug or feature spec / result, fid into chat message attachments; one fid can be attached in several places. With dataBase64 (up to 2097152 bytes) the file is saved at once. Without it, provide the exact size in bytes (up to maxSize), PUT the file to uploadURL using the required headers from the ticket (Content-Length must match size), then complete the upload by calling file_upload with fid. Files cannot be deleted through MCP.

Returns a file's metadata (name, mime type, type, size, upload date and author) and a signed, time-limited download URL by fid - for video, archives, design assets and other files not returned inline; downloadURL is null where the storage has no signed links. Access follows the items the file is attached to; a design file ID no longer found was replaced by a re-import. attachToken can be inserted into a spec / result as is.

Saves a confirmed fact, rule or recipe as an agent memory record when the user asks to keep knowledge for future agent work; secrets only at the user's direct request. The record starts personal and unverified: it applies to the token owner's agents at once, and a moderator can make it shared. level is the scope: company (Git, cloud, CI), user (personal preferences), project (stands, addresses, project infrastructure) or repository (conventions, tests, code pitfalls).

Deletes an agent memory record at the user's request: authors their own, moderators (memory:moderate) any but user-level ones. Rejected if the record changed since the given version.

Lists agent memory records visible to the user, with filters and usage statistics: deliveredCount (delivered in full), readCount (read by ID), lastUsedDT. Useful for finding duplicates before saving a record and for reviewing, moderating and cleaning up memory: with memory:moderate it covers all company records except personal ones, verified = false is the moderation queue, sort = usage with unusedDays finds rarely used records.

Returns agent memory records and MCP rules in full by ID (rules by slug, e.g. git; memory records by UUID). Useful when a record from the memory index is relevant to the user's task; unavailable IDs come in notFound.

Updates an agent memory record at the user's request; passed fields are replaced, and a new level, projectID or repositoryID moves it. Authors edit their own records, moderators (memory:moderate) any but user-level ones; an author's edit makes the record personal and unverified again, while a moderator's edit keeps these flags; verified and shared (shared needs verified) are a human moderator's decision. Rejected if the record changed since the given version.

Creates a product module (without moduleID; productID and title are required) or updates a module's name, description, parent or components, or removes its main Figma frame; omitted fields stay unchanged. Only at the user's request or with their consent: the product structure belongs to the team.

Returns a product's working context: project, spec excerpt (full spec with includeSpec), product analyst and product lead, unfinished versions with defaultVersionID (the default for new work), repositories and design files. With job, it also returns the workspace conventions and team notes for that kind of work (memoryInstructions) and the memory index of its other notes (ID → title), as reference; notes for other kinds of work are not listed: memoryOtherJobs gives their count per kind of work, and they come in this product context when that kind of work is in job. Notes come in full while the response stays within 44 thousand characters (the client's output limit): a note that does not fit is listed first in the index, and a line above the text gives their number. qaDevices holds the company's QA devices: in full with job qa, in brief with dev and analysis. It also returns the variables that apply in work on the product's tasks for that kind of work (variables), all levels together: for the same path and key the more specific level wins (company, project, repository, user, token); description and location, values of short non-secret environment variables only.

Lists projects with their active products (archived products are excluded); projectID narrows the list to one project. Useful for choosing the product to work in.

Returns the product structure for tagging tasks and bugs: modules (componentIDs link to the shared components list) and components; a module does not imply its components. desc and design (the main Figma frame: snapshotFID - snapshot, contextFID - layers) are returned only for items in IDs; query filters by name.

Changes a product (only the passed fields) and returns its updated context; isArchived moves it to the archive with its versions, features and tasks, taking them out of work selection. Changes shared product structure; only at the user's request or with their consent.

Returns line-by-line blame of a file at a ref: ranges (lines attributed to a commit sha) and commits (title, message with task keys, author, dates). Blame at the parent of a fix commit shows the lines as they were before the fix. Up to 204800 bytes (large files in ranges via startLine/endLine); renames are not tracked.

Returns the diff between two refs without truncation: by default from the merge base of from and to, as in an MR; straight compares with from directly (e.g. a previous review's sha). Patch lines carry new-version line numbers; pages are up to 153600 bytes (next page: offset = nextOffset until null), and a file that does not fit comes with error plus baseSha and toSha.

Returns an overview of a product repository: git provider, URL, default branch and its sha (defaultBranchSha), linked projects, agent access level, the start of the README (up to 16384 bytes) and the technical passport (stack, architecture, conventions; stale - may be outdated). Useful for an unfamiliar repository; reads at a sha from the responses are served from the cache.

Reads files at a ref: one file (path) or up to 20 parts (files) - whole files, line ranges or declarations (symbol: a function, class, method or type with its leading comment, found heuristically). Up to 204800 bytes per response, so large files are read in ranges via startLine/endLine (totalLines is returned); a failed part carries its own error without affecting the others.

Returns the commit history of a ref, file or directory, like git log, paginated: message, author, dates, parents, task keys from the message (taskKeys) and linked tasks (tasks); hasMore marks a next page.

Shows who changed lines startLine-endLine of a file and in which task, from commits synced to Kosmodrom across all branches, newest first (linkType: message - task key in the message, branch - commit on the task branch; match=path - no line ranges for that commit). Lines shift with later edits, so results are candidates; only task-linked commits are included, up to 100 (truncated beyond).

Searches code at a ref (task branch, tag or sha) like git grep, returning path:line: text lines: query - a literal string (case-insensitive unless caseSensitive), queries - up to 10 strings, regex - a per-line JavaScript regular expression that filters query matches or, without query, scans the files under path. Up to 200 lines and 50 files per query (truncated beyond); an empty result means no match at that ref.

Lists a repository directory at a ref: up to 500 entries, 1-4 levels below path (truncated when cut off). The response includes the resolved sha.

Returns the token owner (signed-in user), the company and the language of its data, token scopes, the owner's privileges (allows) and token expiry (expiresAt; null - no expiry). Also includes the company's and user's conventions and notes for AI agents (memoryInstructions) with an index of further memory records (memory: ID → title), as reference material. Also returns the company's, user's and token's variables for AI agents (variables): description, file path (file) or environment variable name (env), and the value of short non-secret environment variables only. In work on a task, the variables of the product context apply.

Returns a task's code: product repositories (main one first), live branches with the task key, commits with stats and paths, the task's MRs (link; review threads stay at the git provider) and reading hints. Useful when the user asks how a task is implemented or wants it reviewed.

Returns a task or bug by ID or number (unique within the company): spec, gist (gistInfo.stale - the spec changed after the gist), category, type (severity for bugs; bugType - defect nature), feature (feature.spec with includeFeatureSpec; the full feature plan is in the feature context), relations (dependencies - what it waits for; blockedTasks - what waits for it), allowedActions, specRevision, productID and a page of the task chat. Imported designs are in designs (design: markers; snapshotFID, contextFID with contextSize, assetsFID) the design block holds design files and the main frames of the task's modules (for visual work), and attachments are in attaches by fid; raw design links without a designs entry are not imported. Useful when the user mentions a task number or asks about a task.

Creates a task (not a bug) and publishes it right away: with an approver it goes to approval, otherwise to work to the assignee. rulesRevision is the current revision of the workspace's task creation template for the type, and spec is checked against that template; placement is one of featureID / featureKey (product and version from the feature), versionID (no suitable feature) or productID (product backlog). Stage assignees: employee uuid, "any" (any employee) or null (no such stage; the work stage always exists). Returns link, status and available transitions.

Deletes a task or bug (shared team data). Irreversible: deletion is soft, but there is no way to restore the task; only at the user's direct request. Finishing the work on a task is not deletion.

Finishes the work on a taken task (shared team data): outcome, result, message and usage in one call. Outcomes: done (the work is done or accepted and the task moves on), return (sent back with a required message, including bugs in work returning to testing), wait (the part is done, the task waits in the queue), close. The server makes the transition, closes the worklog and calculates the cost of the work from the difference of the start and end snapshots.

Saves a task stage evaluation when the user asks to evaluate work: a recommended bonus factor and a comment, visible to all who see the task. One evaluation per stage (a new one replaces the old); the server marks it final or interim by whether the task is closed, and the factor is a recommendation that does not change tracked time.

Returns the data for evaluating a task stage when the user asks for a work evaluation, together with the workspace's evaluation rules for the task type and stage (rules: content and the rulesRevision an evaluation carries): spec and result, the stage assignee with level, rates, time and cost, plan and time by status, returns, bugs and regressions with fix cost, commits and the previous evaluation. Money requires task:costs for the task, otherwise null; null salary and bonus are hidden. Rates and amounts are for the assessment, not for the evaluation comment.

Publishes the token owner's own task or bug draft without taking it into work (shared team data), like the "Publish" button in the web: the draft goes to approval if an approver is assigned, otherwise to work to the assignee. Items created through this server are published at creation; a draft appears when the approver returns the item for fixes. Returns link, status and available transitions.

Deletes a task relation addressed by key, otherKey and role, as in the task's relations; removing dependencies / blockedTasks unblocks the waiting task. Irreversible; only at the user's direct request, after the user confirms what will be affected.

Creates or changes a relation between two tasks or bugs. The role is relative to the current task (key), with the names used in the task's relations: dependencies - the current task waits for the other; blockedTasks - the other waits for it; duplicateOf / duplicates; regressionOf / regressions; foundDuring / findings; related - neutral. For a bug, foundDuring is the task during which it was found and regressionOf the task that introduced the defect (by git history only). Without a relation of that role one is created (desc - explanation); an existing one gets newRole and desc. Moving it away from dependencies / blockedTasks unblocks the waiting task with notifications, as in the web app.

Searches a product's tasks and bugs by meaning - titles, gists, specs and results, tolerant to word forms and typos - when the number is unknown; task numbers such as "#12345" are rejected as queries. allowClosed includes closed tasks; the next page takes the last item's cursor with the same query and filters.

Returns the context for updating a task's or bug's spec: spec, feature, recent chat, a code summary (basis=actual, with git read access) and the workspace's spec-update guidelines (instructions); writes nothing. mode=analyze - for "check, compare, propose" requests (differences and a full new version); mode=apply - when the user asks to update or sync. basis=requirements - "from the chat"; basis=actual - "from the code, as built".

Takes a task or bug into work or returns to it (shared team data). The server picks the transition: a draft is published, a task in deployment goes back to work, an "any" stage is assigned to the token owner. A closed task is reopened on the token owner: they become the work assignee, the plan with its AI estimate and the closing resolution are cleared, a bug leaves its version; the approver, reviewer and tester stay. When the user decides that the previous assignee continues the work, their workAssignee is noted before the take; after it come finishing with wait and then a task update setting them as workAssignee. Another employee's stage is refused. Returns the job for the task, the available outcomes, where the task goes on done and on return, the task context and, once per session, the conventions for the work on a task and the memory for the job, unless the product context with the same runKey already delivered it.

Edits a task or bug (shared team data); only the passed fields change: title, spec, gist, result, priority, labels, placement (featureID or featureKey, featureID null removes it from the feature; versionID; productID), work iteration, bug fields (build, bugType, stage, browser, devices, fuzzy), type within its kind, modules and components (full new lists), stage assignees and ord. Stage assignees: employee uuid, "any" (any employee) or null (no such stage; the work stage always exists). Status is not changed here; returns link, status, specRevision and changed.

Searches company employees by name, phone, email, department (role) and level; filters combine. With userID, returns one employee with the full profile, access and roles. Each employee comes with link (the name as a link) and mention (for a Kosmodrom chat message).

Saves a variable for AI agents when the user asks to keep a value: an access, a token, an address or an environment setting. A secret (secret) is stored encrypted and is never returned in responses. If a variable with the same level, scope, path and key exists, the passed fields are replaced. Levels company, project and repository require memory:moderate; user and token are the user's own. With path the value is the file /run/agent/vars// on the agent VM, without path it is the environment variable key.

Releases a version: marks it completed with a release date, after which it is not offered for new work; isPublished also publishes it. Without releaseDT the version keeps its existing (possibly planned) date or gets the current date if it has none; the response has the resulting releaseDT. Irreversible; only at the user's explicit request.

Creates a product version (without versionID; productID, major and minor are required, the title is built by the server) or changes a version's number, notes or design file (only the passed fields); does not release it. Changes shared product structure; only at the user's request or with their consent. Returns the version.

Lists worklog (time-tracking) records of tasks and bugs for time and cost reports; filters by task, feature, employee, period and task status combine (none - all accessible records), meetings excluded. Amounts the user may not see come as 0, meaning hidden, not unpaid; isActive marks ongoing work whose time and cost still grow. totals covers the whole selection, employees and tasks are in the users and tasks dictionaries, and the next page comes with nextCursor and the same filters.