team repo

Repo Commits

The log — one page of it, newest first, with each commit's BODY.

The body is not decoration here. A runtime commit says what work it was in the subject and then names the run (turn: run <uuid>) and every file it touched with that file's title underneath. Dropping it to save bytes would throw away the only link between a change and the conversation that caused it.

act is the other axis: not "what changed" but WHAT THE BUSINESS DID. It matches git's own --grep against the Act: index line, so finding every call this month never opens a single commit body — and it composes with since, which is the difference between ~15 ms and ~1 s per 100k commits.

get/v1/teams/{team_id}/repo/commits

Request

  • Base URL: https://api.stormy.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.stormy.ai/v1/teams/{team_id}/repo/commits
  • Auth: none declared

Path parameters

team_idstring uuid required

Query parameters

refstring
pathstring
authorstring
sincestring
grepstring
actstring
skipinteger
limitinteger

Headers

authorizationstring nullable
x-darwin-tokenstring nullable

Response

Successful Response

object required

Changes

No operation changes recorded.