Synopsis
Description
Prints who you’re signed in as, which organization is active and what your role in it is, and which project and branch this directory is bound to. Below that it lists every organization you’re a member of and marks the active one with a ●, so a multi-org account can see at a glance which org the session actually resolved to.
Useful when a command isn’t doing what you expect and you need to check what Capy thinks the current context is.
Example
Any field Capy can’t resolve prints as —. Role is best effort: if the member lookup fails, it falls back to — rather than blocking the rest of the output.
Outside a project
capy info doesn’t need a keep.lock. Run it anywhere and you still get the session view - the project fields show —, and Active Org is annotated (session default — not pinned by keep.lock) instead of (from keep.lock), or none when the session isn’t scoped to an org at all.
If your cached session has expired, capy info opens the browser sign-in flow when the directory has a keep.lock, then prints the table once you’re back. Outside a project - or if that sign-in fails - it prints Not signed in. Run capy to authenticate. and exits 1.
capy info is disabled in local-only mode - local mode has no organization, team, or server for it to report on.Last modified on August 11, 2026
