first-tree-cloudlisted

# First Tree CLI — Cloud Layer ## Overview Use this skill to map a user's First Tree Cloud / collaboration intent onto the right `first-tree` command or code path without re-discovering the repo each time. (For Context Tree onboarding and validation, the right skill is `first-tree`; for the GitHub notification daemon, it's `first-tree-github-scan`.) Keep the mental model straight: First Tree Cloud is the communication and identity backbone for agent teams. It is **not** the agent framework, not the orchestration engine, and not the Context Tree. First Tree Cloud has three principals: - **Server** — operated centrally as a SaaS by the First Tree team. Owns identity, persistence, admin surface, and the inbox. End users do not run their own server; the CLI has no `server` command group. - **Client** — one per computer. A machine signs in with a First Tree member's credentials once, then runs every agent pinned to it. - **Agent** — many per First Tree organization. Lives in the server's database; is bound to exactly one client machine. This shape drives almost every command: `daemon` and `config` target this machine, `agent` targets a row in the server's database (usually acting as the member via their own JWT). ## Start Here 1. **Classify the task before acting.** Most requests fall into one of these buckets. Pick the bucket, then go to the reference it names. - Install or sanity-check the CLI on a fresh machine → `references/command-surface.md` - Connect a computer