Search project memory
What the project already learned from the tickets it shipped — the decisions the team made in answered questions, what QA found, which files a feature lives…
What the project already learned from the tickets it shipped — the decisions the team made in answered questions, what QA found, which files a feature lives in, the PR that shipped it, and the requests that were turned down. Every entry is derived from the item's own records (investigations, questions, QA notes, linked PRs) and is rebuilt whenever those change, so it never disagrees with the ticket.
Search with q (free text), paths (comma-separated files or
directories — entries that touched them rank first), item (a queue
item — its title and description become the query, and its own entries
are left out) or trail (a trail — its title, intent and goal become the
query; its own and its items' entries are left out). With none of them, the newest entries come back. Bodies are
capped; read the full ticket with ops get <item>.
A coding agent picks up a ticket and, before reading the
repo, asks what was already decided and built around it:
ops memory search --item 42.
Authorization
bearerSdkKey Pass an admin SDK key as Authorization: Bearer sdk_admin_…. Mint via POST /api/admin/keys with type: "admin".
In: header
Query Parameters
Free-text query, e.g. checkout retry.
1 <= length <= 500Comma-separated repo-relative files or directories, e.g. apps/web/src/checkout/,packages/billing/src/retry.ts.
1 <= length <= 2000A queue item — its per-project number (e.g. 7) or full id. Its title and description become the query; its own entries are excluded.
1 <= length <= 128A trail — its handle (e.g. T-12) or full id. Its title, intent and goal become the query; its own entries and its items' are excluded.
1 <= length <= 128Only entries of this kind.
"shipped" | "declined" | "decision" | "qa" | "outcome"Maximum entries to return (1-50). Defaults to 10.
1 <= value <= 50Header Parameters
Project the request operates on. Optional — defaults to the project the SDK key belongs to; pass it only to scope a multi-project key (the generated client sets it once from its configuration, so per-call callers never thread it).
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://shipeasy.ai/api/admin/ops/memory"{
"entries": [
{
"id": "string",
"kind": "shipped",
"title": "string",
"body": "string",
"paths": [
"string"
],
"prUrl": "string",
"item": {
"id": "string",
"number": 0,
"type": "bug",
"title": "string",
"status": "open"
},
"trail": {
"id": "string",
"number": 0,
"handle": "string",
"title": "string",
"phase": "planning"
},
"occurredAt": "string",
"score": 0
}
],
"terms": [
"string"
]
}{
"error": "Malformed request (bad JSON, missing project scope).",
"code": "BAD_REQUEST"
}{
"error": "Missing or invalid admin SDK key.",
"code": "UNAUTHORIZED"
}{
"error": "Key is valid but not allowed to act on this project.",
"code": "FORBIDDEN"
}{
"error": "The resource does not exist or is not visible to the caller.",
"code": "NOT_FOUND"
}{
"error": "The request body failed structural (schema) validation.",
"code": "VALIDATION"
}List queue activity
The activity feed of the project's queue items, newest first: every status, priority, owner, tag and content change, every comment, every alert…
Show an item's trail
Alias. Kept for the v1 item routes: it resolves the item's trail and behaves exactly like GET /api/admin/trails/{handle}, answering 404 when the item is on…