v20260828

The CLI can now say which actor your API key is.

memorylake actor me
memorylake actor me | jq -r .id

{
  "id": "actor-fd25f63e…",
  "custom_id": "user::e7f4fbd1…",
  "actor_type": "HUMAN",
  "display_name": "…",
  "tags": [],
  "created_by": "user::e7f4fbd1…"
}

Until now a script that needed the caller's actor had to list actors and guess,
usually by preferring the first HUMAN. That is wrong the moment an account has
more than one person in it — which is the normal case for a shared workspace.
The server answers directly now, and the CLI passes the answer through.

The output is the same record shape actor get returns, so anything already
parsing that needs no change.

It is not necessarily bound to a workspace

Worth knowing before you build on it: a result does not mean that actor can
write in any particular workspace. The actor comes with the account; joining a
workspace is a separate, explicit act, and in a freshly set-up account the two
have often not met.

memorylake actor me                        # who the key is
memorylake actor list --workspace <ws-id>  # who can write there
memorylake actor bind --actor <id>         # put one in the other

So a flow that offers "pick an actor for this workspace" cannot assume the answer
from actor me appears in that list — it may need to offer binding it first.

Failure behaviour

Every API key has an actor, so there is no "you have no actor" outcome to handle.
That makes a 404 unambiguous: it can only mean the server predates this endpoint.
The CLI says exactly that rather than surfacing a bare NOT_FOUND, which would
read as "you have no actor" — the opposite of the truth. The server's own message
is kept underneath so a real failure stays diagnosable.

Authentication and network failures take the paths they always did.

Why me and not default

default is already a concrete name in this CLI — it is the default profile,
which auth status prints — so memorylake --profile work actor default would
read two ways. It would also sit beside memorylake actor get default, a legal
command with an entirely different meaning, since custom_id is caller-defined
and an actor may genuinely be called default. And default here has always
meant something you chose and can change; this is neither.

Also

Actor output now includes created_by, which the API has been sending and the
CLI was dropping on the floor.

Upgrading

Re-run your install command. Nothing else changed.

---

What's Changed

• feat: Add actor me, the actor a key represents by @a1594834522-coder in #29

Full Changelog: v20260827.1...v20260828