Tool
pins_near
Description
List pins touching the code a task involves. Call it when you start one: there may be known bugs, gotchas or an in-flight fix. Pass files, directories (ending in /), or both. By default you get pins on those files and anywhere in their folders; raise radius to look further up the tree. Closest pins come first; among equals, pins that point at lines or a symbol in the file before ones that only list it, then claimed ones (work in flight). Each comes with its closest match, with the pin's lines and symbol there when it gave them (more_matches counts the rest). get_pin any that matter to your change. scope in the result lists the folders searched; it's empty when none of your workspaces has pins in the repo.
Parameters
repostringrequiredRepository as owner/name, from the git remote. Picks the workspace: the one with pins in this repo.
workspacestringWorkspace slug. Only when the repo has pins in several of your workspaces, or in none yet; otherwise the repo picks it. - acme: Acme (acme/api) - acme-mobile: Acme Mobile (acme/ios)
Your workspaces, e.g.acmeacme-mobile
pathsstring[]requiredFiles and/or directories (ending in /). Repo-relative, e.g. src/auth.ts. Never absolute. A line range (src/auth.ts:40-88) is ignored.
1–50 items
radiusintegerHow far up to look. 0 = only the exact files (directories: only files directly inside). 1 (default) = anywhere under each path's folder. 2 = anywhere under the parent folder, and so on. Max 5.
0 to 5
include_resolvedbooleanInclude resolved and dismissed pins. Default false.
limitintegerDefault 5, max 50.
1 to 50
all_matchesbooleanList every matching path pair per pin instead of only the closest. Default false.
Response
An example. The result sits in the same envelope as every tool's; see Responses.
Input schema
Exactly what tools/list sends your agent.