---
title: "Repo Recent Files"
method: GET
path: "/v1/teams/{team_id}/repo/recent-files"
tags: ["team repo"]
---

# Repo Recent Files

`GET /v1/teams/{team_id}/repo/recent-files`

## 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/recent-files`
- Auth: none declared

The files this workspace touched most recently, newest first.

A directory listing answers "what is in here"; it cannot answer "what just
happened", which is the question somebody opening a live workspace actually
has. The tree's own recency is per FOLDER — `customer/` changed a minute ago
tells you nothing about which of its twelve files did.

One history walk, taking the first commit that touches each path, the same
trick `_annotate_last_commits` uses for a single directory level. Deleted
paths are dropped: a link to a file that is gone is worse than no link.

## Path parameters

- `team_id` string, uuid, required

## Query parameters

- `ref` string
- `limit` integer

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/4d811ab18158?raw)