Skip to main content
agentx gives each computer a machine id and a label. The id identifies the machine in scans, snapshots and the commits agentx writes. It stays the same when you reinstall agentx. The label is a readable name that you can change. The same command shows where agentx keeps its files on this machine.

Show the machine

Derivation tells you where the id comes from:

See where agentx keeps its files

The last four rows say where agentx keeps its files on this machine: The size counts the files in account.git alone. The worktrees of your own skills, under worktrees in agentx home, are not part of it. There is no cache to clear: what agentx fetched from your sources lives in the account repo. With --json, the machine event carries the same as home, settings_file, library, account_repo and account_repo_bytes. The last two are absent until the account repo exists. See Environment variables for AGENTX_HOME and AGENTX_LIBRARY.

Rename the machine

Until you set a label, agentx uses the hostname. You can also set the label with agentx config set label. The label must be one line of at most 256 bytes, with visible text and no control characters. agentx rejects any other label with exit code 1.

Reset the id

Reset the id when two computers show the same id, for example after you clone a virtual machine. The new id is random. agentx keeps using it until you delete machine.json in agentx home. agentx then computes the id from the platform id again, or generates a new random id if the computer has no platform id. If another agentx command is running, rename and reset-id stop with exit code 7. Run them again when that command finishes.