---
title: memhtml entity activity
description: Every entity with its file count and its last activity, newest first. Report only.
---
## 1. Synopsis
Every entity with its file count and its last activity, newest first. Report only.
```sh
memhtml entity activity [options]
```
## 2. Arguments
This command takes no positional arguments.
## 3. Flags
| Flag | Type | Default | Values | Description |
| --- | --- | --- | --- | --- |
| `--type` | string | *no default* | *no fixed set* | Restrict to one entity type, e.g. `service`. The half before the colon in a `type:name` reference. |
| `--limit` | integer | `50` | *no fixed set* | Rows to return, 1 to 500. An ask outside that is clamped into it rather than refused, and `limit` echoes the bound the answer was built under. `entityCount` is the total matching the scope, so a clamped answer is visible. |
| `--include-archived` | flag | `false` | *no fixed set* | Aggregate archived memories too. Excluded by default: eviction is a `git mv`, so an archived memory still exists and would otherwise keep an entity looking active. |
Every command also accepts the [global flags](/reference/global-flags/).
## 4. Response
On success the command writes one JSON envelope to stdout, and its `type` is `entity.activity`.
On failure it writes the failure envelope, whose `code` comes from [error codes](/reference/error-codes/).
[The JSON envelope](/reference/envelope/) gives the fields both shapes carry. [Response types](/reference/response-types/) lists every value `type` takes across the binary.
## 5. Further reading
No guide block names this command. The [guide](/reference/guide/) is the workflow prose the CLI ships beside the command table: which command to reach for, and in what order.
## 6. Provenance
A loader generates this page from `apps/cli/src/commands.ts` while the site builds, so no file in the repository holds it: the `COMMANDS` array there is the one source of argument parsing, of `memhtml manifest`, and of `AGENTS.md`. Change the registry and this page changes with it.