MCP changes by release
Agents read Projektor’s tool descriptions when they connect, so a new release reaches
them on their next connection. Some MCP clients cache the tool list for a whole session:
reconnect, or restart the client, after you upgrade. Prompts, scripts or skills written
against an older release may rely on fields or errors that have since changed. This page
lists those changes, newest first. The REST API (/api/*) is not covered here: its rows
keep the full shape.
v0.11.1
Section titled “v0.11.1”- Closing with a token is audited with or without
agentSessionId. Adonetransition made with an API token or OAuth grant is treated as agent-initiated when it closes an issue an agent has leased, or supplies acompletionReport. Freeform verification then setsneedsAudit:true, where leaving outagentSessionIdused to avoid it. To stay unflagged, put a PR, CI run or commit link incompletionReport.verification. - A bare commit SHA must mix digits and letters to count as evidence. A plain number
or a hex-looking word in
verificationno longer clears the audit. A link is the reliable form. list_commentsitems carryagentSessionIdwhen an agent session wrote the comment (completion reports, and comments sent withcreate_issueorupdate_issuealongside anagentSessionId). Other comments are unchanged.mark_wiki_notifications_readaccepts its full 200 ids. More than about 98 used to fail on a deployed instance.list_issuesprioritiesignores unknown and repeated values. A filter made up only of unknown values still matches nothing.
v0.11.0
Section titled “v0.11.0”list_messagesreturns{items, next?}like the other paged lists, instead of{items, nextCursor}. Passnextback ascursor; the cursor value is unchanged. The REST endpoint still returnsnextCursor.
v0.10.2
Section titled “v0.10.2”release_filestakes a session name asagentId. It resolves among your credential’s active sessions, live ones first. A name that matches none, or several, is a validation error that lists them.issueRefandissue_refnow name the issue on every tool that takes one.get_flow_metricscollaboration and health figures were redefined. The REST/flow-metricsendpoint changed too. Figures from earlier releases aren’t comparable. See Flow metrics.humanInterventionscounts review decisions (bounces out of review plus the sign-off), not comments.autonomyRatioandflowEfficiencyskip issues that never held an agent lease.factoryHealth.abandonedClaimscounts sessions that went silent holding claims, once each, rather than every claim a cleanfinish_workleft open.
v0.10.1
Section titled “v0.10.1”fieldsreturnslabelsas an array.list_issues,get_issueandget_issueswithfieldsnaminglabelsreturned the raw JSON string ("[\"a\"]"). They now return an array ([]if the issue has none), the same as thefullview.verbose:truestill returns the raw row.- Label search, label filters,
get_prioritized_issuesand the project list read far fewer rows. Results are unchanged.
v0.10.0
Section titled “v0.10.0”Results that changed shape
Section titled “Results that changed shape”| Tool | Before | Now | Old shape |
|---|---|---|---|
list_issues |
full rows (without body) |
summary rows {ref, title, status, status_key?, priority, type?, parent?, assignee?, updated, rollup?}: no id, labels, timestamps, links, customFields or url |
view:"full", or fields:[…] for just what you need |
list_issues |
parent was the parent’s id |
parent is its ref (PROJ-42), omitted when the parent is in a project you can’t see; full rows carry parent_ref |
verbose:true |
get_issue |
links were raw link rows |
each link is {type, ref, title, status?} (list_issue_links still returns link ids) |
verbose:true |
start_work |
session, lease and claim rows | {sessionId, leaseId, paths, issue}, where issue is the claimed issue as get_issue returns it |
verbose:true |
register_agent |
the session row | {id, name} |
verbose:true |
claim_issue |
the lease row | {leaseId, issueRef} |
verbose:true |
finish_work |
session and issue rows | {sessionId, issueRef, status?, followUp?} |
verbose:true |
list_active_agents, list_issue_leases |
raw rows | {id, name, issueRef?, live, startedAt, lastHeartbeatAt}; lease rows drop workspaceId and issueId |
verbose:true |
get_issue, get_wiki_page, get_playbook |
add version. Pass it back as ifVersion and an unchanged result comes back as {unchanged:true, version} |
omit ifVersion |
|
update_wiki_page, patch_wiki_page, verify_wiki_page |
{ok, url} |
{ok, url, revisionId}; pass revisionId as the next baseRevisionId (create_wiki_page returns revisionId: null) |
|
get_tool_usage |
counted from D1 | read from Workers Analytics Engine, adding avgLatencyMs and per-tool errorCodes. Returns available:false until the deployment configures read-back (see Deploying); history recorded before the upgrade is gone |
Calls that now behave differently
Section titled “Calls that now behave differently”-
list_wiki_changes:sincewas required; it now defaults to seven days ago. -
Stale agent sessions are revived.
claim_issue,claim_files,post_messageandupdate_issueused to fail with “Agent session is not live” once a session’s heartbeat expired. They now revive it, but only for the credential that registered it. Ended sessions still fail. -
start_workchecks for a live lease conflict before registering a session, so a conflict no longer leaves an ended session behind. -
Lease conflicts name the holder:
PROJ-42 is leased by agent "x" (session …), claimed N min ago, withdetails {holder, issueRef, leaseAgeMinutes}. Pick another issue rather than retrying. -
Wiki conflicts that carry a diff name the revision to retry from, as
baseRevisionId=<currentRevisionId>. -
create_issuestraight intoin_progress,in_reviewordonestamps the same flow timestamps as an update, so those issues now count incompletedAfterfilters and flow metrics. WithagentSessionId, creating intoin_reviewordoneneeds acompletionReport, asupdate_issuedoes. -
update_issuerejects:- a
commentwith nothing else to change (useadd_comment); bodytogether withappendBodyorbodyEdits;- a
bodyEditsfindthat matches no text or more than once, in which case nothing in the call is written; - a resulting body over 50,000 characters.
A body edit that races another change to the body returns a conflict instead of overwriting it.
- a
- Tools:
create_issues: up to 50 issues in one call, with a per-item error for an item that was rejected;create_issue_links: up to 100 links, also with per-item errors.
create_issuetakesagentSessionId,completionReport,commentandlinks:[{type, target}], all committed together.update_issuetakescomment,appendBodyandbodyEdits:[{find, replace}].get_prioritized_issuestakesbodyChars(0–1000) for a body preview.list_wiki_pagestakessort(titleorupdated) andlimit(1–500).get_projectaccepts a project’s URL slug as well as its id.get_flow_metricstakesagingWipLimit(1–50, default 10) andverbose.
See Response conventions for view,
fields and verbose.
Built by Verdient.