Find the durmem setup, maintenance, store-management and coordination commands. The durmem command (the CLI) connects this computer and its coding harnesses to your durmem server; it is not the server. For everyday memory, ask your connected harness or agent to save or recall facts; CLI memory verbs are for internal use.
Run durmem --help for the command list and durmem COMMAND --help for current options, parameter types and defaults. Help needs no store and sends no request. Check your installed version with durmem --version.
| Task | Commands | Guide |
|---|---|---|
| Connect this computer | setup (hosted-setup alias), login | Install and set up |
| Maintain this computer | update, uninstall | Install and set up |
| Inspect connections | list_stores, describe_store | Manage stores |
| Create, recover or remove stores | create_store, unlock_store, set_store_domain, logout, revoke, drop_store | Manage stores |
| Coordinate agents (optional) | whoami, kanban_init, publish_task, claim_run, record_capability_assessment, post_message | Kanban |
| Operate worker fleets (optional) | fleet, residual | Kanban |
setup configures supported harnesses; login only authenticates and registers stores. When selecting a private server explicitly, pass its HTTPS web origin after the command: durmem setup --base https://durmem.ai or durmem login --base https://durmem.ai. Server administration uses durmem-admin server, not durmem setup. See Private server installation.
durmem [--store NAME] <tool> [--params '<json object>' | --params-file PATH]
durmem <built-in> [options]The public CLI supports setup, store administration, and optional coordination. Built-ins use their own options, not tool JSON. Fleet and residual pass remaining arguments to their own parsers. Put their global flags before the subcommand and check their help.
--params and --params-file are mutually exclusive. With neither, parameters are {}. A file must contain a UTF-8 JSON object, not an array.--params-file for nested JSON or cross-shell scripts. Never put credentials or email codes on the command line or in committed parameter files.setup and login --json still need an interactive terminal when sign-in is required; prompts go to stderr. With matching saved credentials, setup can repair or update harnesses without another sign-in. Use --harness to select one explicitly.Store-management commands name their configured section in parameters; see Manage stores.
Each CLI invocation is a new process. An explicitly named store is connected for that invocation; this does not change persistent configuration. See stores.toml for persistent defaults and workspace mappings.
list_stores lists local configuration, not proof that a server store exists. describe_store can return a live_describe_error while exiting successfully; inspect its result.
| Code | Meaning |
|---|---|
0 | Command succeeded. |
1 | Cancelled: setup/login (for example consent declined) or uninstall not confirmed. update also uses 1 when it cannot run the installer: no recorded installation server, a Windows runtime that must be repaired first, or a failed download. Launchers and Fleet commands also use 1 for their own failures. |
2 | Usage/input error or command failure, including a tool call that exceeds its 30-second limit and an uninstall that stopped before completing. It does not prove no request reached the server. |
3 | Partial or unsettled lifecycle result, partial harness setup, or a store operation that did not confirm success. |
130 | Interrupted with Ctrl-C. Anything already sent to the server may have completed. |
| other | update returns the installer's own nonzero status if the installer fails. |
For a normal result, drop_store returns 0, 2 or 3: 0 means the server confirmed deletion and the CLI removed the local section (or found it already absent); 2 means a usage or operation error; 3 means completion was not confirmed and the store may or may not have been destroyed. On 3, the local section is kept: check the server before retrying. drop_store does not use 1 for cancellation; confirmation is the exact repeated section name.
Read the exit status and JSON/result details. Pending creation, owner verification and an unknown write outcome are not completed operations. See Troubleshooting.
Store lifecycle tools use the section's recorded web_origin, not the gateway endpoint. Setup/login server selection and private certificate trust belong to Install and set up. For a private server, use its HTTPS web origin with --base after setup or login, including when the server uses a private IP address.
Unless you set auth_store, create_store uses the first section in file order with an endpoint—not the top-level default or alphabetical order. unlock_store also accepts auth_store. drop_store does not; it uses the first endpoint-bearing section. A dead or wrong-server credential section can block the operation. A section without web_origin denotes the hosted origin, https://durmem.ai.
logout forgets one section locally. It does not revoke its key or delete data. Move the default to a remaining section before logging out of the default while other stores remain.revoke returns an owner-verification browser URL on the recorded origin (exit 3). Opening and confirming the URL in a browser rotates the key; receiving it alone does not. Get replacement keys from that server's /stores panel. Every old-key client must reconnect, but data stays intact. The CLI refuses missing origins and direct/legacy connections.drop_store SECTION --confirm SECTION permanently destroys server data. If the outcome is unknown, the CLI keeps the local section. Check the server in the web app or with the administrator before retrying. Local list_stores cannot confirm deletion.create_store may already have succeeded. Reconnect to the same server with durmem login --base https://durmem.ai for a private install (or durmem login for the hosted service), using the same email, then check that server instead of creating a duplicate.Use your connected harness or agent to save or recall facts. CLI memory verbs are for internal use.
Kanban tools must use the current harness-native session identity, not a fabricated id or another worker's id. whoami reports that agent identity, not your hosted account. A one-shot script may publish ownerless work as script@<name>, but cannot claim work, send messages, write worker events, or declare itself an owner. Follow the Kanban guide and installed skill for enrollment, events, and ownership. Ordinary single-computer memory use does not require Kanban.
For the commands below, use durmem COMMAND --help (or just durmem --version for the version). Use the full name or short alias for tools. These are purpose summaries, not a second parameter catalog.
setup#Connect supported harnesses; follow the prompts. See Install and set up.
login#Register store credentials without configuring a harness.
update#Re-run the installer from the server this CLI was installed from; the CLI then prints durmem setup --base <recorded-origin> to refresh your harnesses. For a private server, keep its HTTPS web origin in --base, for example durmem setup --base https://durmem.ai. update takes no arguments. An install without a recorded server prints the install command to run once by hand.
uninstall#Stop this computer's durmem Fleet workers and remove the local durmem runtime after you type yes. It keeps stores.toml and never touches server data; it prints, but does not run, the commands that remove the harness plugins.
drop_store#Permanently destroy a server store; see lifecycle safety.
--version#Show the installed CLI version. This top-level flag must be the first argument: durmem --version.
fleet#Manage desired state and credential vault; see Kanban.
residual#Reconcile this computer with Fleet desired state.
loom_create_store#Create an additional store; inspect pending outcomes before retrying.
loom_unlock_store#Unlock a configured store and wait for readiness.
loom_set_store_domain#Change a store's memory discipline/domain.
loom_revoke#Request browser owner verification before rotating a store key.
loom_logout#Forget one local credential, without revoking it.
loom_list_stores#List local configured stores, not live server inventory.
loom_describe_store#Inspect a store and its live connection result.
whoami#Resolve this harness session's native agent identity.
loom_kanban_init#Initialize a board idempotently.
kanban_publish_task#Publish a task with explicit capabilities and dependencies.
kanban_claim_run#Reserve an eligible task execution.
kanban_record_capability_assessment#Record concrete pre-claim capability failures, or clear them.
kanban_post_message#Send a time-limited message to registered agents.