Skip to main content
Profiles keep separate TinyCloud identities, keys, sessions, and defaults on one machine.

​
Common commands

tc profile create also takes --posture (owner-openkey, delegate-session, or local-owner-key) and --operator (human or agent). The profile is chosen from --profile, then TC_PROFILE, then the configured default, then default. The node host is chosen from --host, then TC_HOST, then a discovered local node, then the profile’s host, then https://tee.node.tinycloud.xyz.

​
Inspect a profile

tc context reports the profile, owner and session DIDs, host, space, and whether the local session is present, expired, missing, or has an unknown expiry. It reads local state only and does not test access.

​
Default space

The default space is the short name used when you omit --space on tc kv and tc sql.

​
What each profile stores

  • profile.json for host, DID, owner, posture, and default space
  • key.json for the local keypair
  • session.json for the active session
  • additional-delegations.json and auth-grants.jsonl for imported and granted access
Profiles live in ~/.tinycloud/profiles/<name>/ (or under TC_HOME), with files written 0600 in 0700 directories.

​
Practical use

  • Create one profile for each environment or identity
  • Use TC_PROFILE to pick a default profile in a shell session
  • Use TC_HOST when you want a per-command node override
tc init creates a profile too, so you only need tc profile create when you want a profile without signing in immediately.