> For the complete documentation index, see [llms.txt](https://swu-forge.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swu-forge.gitbook.io/docs/teams/team-battle-log/team-activity.md).

# Team Activity

The **Activity** page is the full, chronological feed of every match the team has logged — the same matches the home **Recent activity** card previews, but complete and paginated. Where the [Team Battle Log](/docs/teams/team-battle-log.md) groups matches into archetype buckets for analysis, Activity is a flat "what has the team been playing lately" list in plain newest-first order.

## Where to find it

From `/teams/[teamId]`, click **Activity** in the header, or **See all →** on the home page's *Recent activity* card. Like the rest of the team feature, it's visible to every member regardless of role; non-members get a 404.

## What you'll see

One row per **match** (a lobby), newest first. Each row reads as *who played what, against whom*:

* The **pilot** (the team member who recorded it) — avatar and name.
* The **deck they ran** — their leader + base.
* The **opponent's** leader + base and aspect icons.
* The match's **W–L–D** across its games, the game count, and how long ago it was played.

The **whole row is a link** — click anywhere on it to open the replay (`/decks/[deckId]/battle-log/[lobbyId]`).

A best-of-three shows as a **single row** with the aggregate record — not one row per game.

The list loads 25 matches at a time; a **Load more** button pulls the next page (cursor-paginated by last-played time, so newly recorded matches never shift a page boundary under you).

## Filters

A filter bar above the feed narrows it. Because the feed is paginated server-side, each filter change refetches from the top with the filters applied (it doesn't just hide already-loaded rows):

* **Played archetype** typeahead — the deck the pilot ran (leader + base group). There's no single "deck" for this page, so this is how you scope to one of your team's archetypes.
* **Opponent archetype** typeahead — the deck they faced (leader + base group).
* **Wins** / **Losses** checkboxes — keep matches with games of the chosen result(s); leave both unchecked for everything.
* **Date** — macros (All / 7d / 14d / 21d / 30d) or a custom from–to range.

Both typeaheads are populated from the team's full history (scoped to the selected [stats period](/docs/teams/team-battle-log/team-stats-periods.md)), so every archetype the team has played or faced is selectable even if it isn't on the currently-loaded page. **Clear filters** resets the bar.

## What counts

The same team-scope rule as the Battle Log: a match appears if it's scoped to this team (has a `KarabastMatchTeam` row — see [Recording scope](/docs/teams/team-battle-log.md#recording-scope)). Intra-team **mirror** matches are excluded, since they're stored twice and would double up the feed.

## Read-only

Activity is a browse surface — match curation (pin, tag, delete) lives on the [Battle Log](/docs/teams/team-battle-log.md) views, so rows here have no action buttons even for owners. Click through to a replay to act on it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://swu-forge.gitbook.io/docs/teams/team-battle-log/team-activity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.