Manage memory collections

The memory command group manages AgentKit memory collections, covering listing, inspection, creation, update, and deletion. The command is also available under the mem alias. A memory collection is a cloud resource for storing and retrieving long-term memory. Creating it does not automatically make an agent write memories. Associate the returned collection ID in the agent or runtime configuration and use credentials for the same provider and region

Creating a collection can incur cloud charges. Conversation and user information written to it is stored by the selected memory service. Check associated agents and retain required data before deleting; --yes skips confirmation

memory list

List all memory collections.

Flag / Argument	Description	Default
`-r, --region <region>`	Cloud region.	auto-detect
`-p, --project <name>`	Project name.	default
`--json`	Output raw JSON.	`false`

agentkit memory list --project demo

memory show

Show details of a memory collection.

Flag / Argument	Description	Default
`<id>`	Memory id, e.g. `m-xxxxxxxx`. Required.	—
`-r, --region <region>`	Cloud region.	auto-detect
`--json`	Output raw JSON.	`false`

agentkit memory show m-12345678

memory create

Create a memory collection.

Flag / Argument	Description	Default
`--name <name>`	Memory collection name.	—
`--description <text>`	Description.	—
`-p, --project <name>`	Project name.	default
`--provider-type <type>`	Provider type (`MEM0` \| `VIKINGDB_MEMORY`).	`MEM0` on Volcengine, `VIKINGDB_MEMORY` on BytePlus
`-r, --region <region>`	Cloud region.	Current cloud provider or environment
`--json <jsonString>`	JSON object merged into the request body (for nested fields such as `LongTermConfiguration`, `VpcConfig`, `Tags`).	—

agentkit memory create --name user-mem --provider-type MEM0

agentkit --provider byteplus memory create \
  --name user-mem \
  --provider-type VIKINGDB_MEMORY

--provider-type values are normalized by casing. BytePlus does not support creating MEM0 memory collections; explicitly passing --provider-type MEM0, or overriding ProviderType to MEM0 through --json, fails before the request is sent.

memory update

Update a memory collection.

Flag / Argument	Description	Default
`<id>`	Memory id, e.g. `m-xxxxxxxx`. Required.	—
`--description <text>`	New description.	—
`-r, --region <region>`	Cloud region.	auto-detect
`--json <jsonString>`	JSON object merged into the request body (for nested fields such as `LongTermConfiguration`, `VpcConfig`).	—

agentkit memory update m-12345678 --description "Updated memory"

memory delete

Delete a memory collection.

Flag / Argument	Description	Default
`<id>`	Memory id, e.g. `m-xxxxxxxx`. Required.	—
`-r, --region <region>`	Cloud region.	auto-detect
`-y, --yes`	Skip the confirmation prompt.	`false`

agentkit memory delete m-12345678 --yes

After creation or update, inspect the returned ID with agentkit memory show <id> --json. If the resource exists but the agent cannot save memories, check the runtime’s collection ID, permissions, and provider configuration. Resource management success does not verify application-level memory reads and writes

Getting Started

AI-Friendly

Command reference

memory list

memory show

memory create

memory update

memory delete