Install
Getting StartedGetting Lyt is one request to your agent, or one command yourself. Install the unified Lyt CLI once — it includes the vault, mesh, skills, and MCP command groups.
Install the CLI
Your agent does not know Lyt yet — it learns Lyt during this setup. So this first request names the package and the steps outright. Paste it to any coding agent you already have.
Set up Lyt on this machine. Lyt is the npm package @younndai/lyt. It requires Node.js 20.9 or newer, and npm. 1. Check whether Node.js 20.9+ and npm are available. If either is missing, stop and tell me exactly what is missing. Do not install a language runtime yourself. 2. Install Lyt globally with: npm install -g @younndai/lyt If this needs administrator approval or fails, stop and show me the exact error. Do not use a different package, a different installer, or a privilege-escalation method. 3. Run: lyt init --auto --json This creates my local setup and also installs Lyt's agent manual and skills into your own instructions, so you know how to operate Lyt in future sessions. You do not need to install those separately. What step 3 actually does, so nothing surprises me: - It creates Git repositories and a first commit on this machine. That is expected, and it stays local. - It may check GitHub to see whether I already have a Lyt setup there and adopt it instead of starting fresh. Tell me which of the two happened. Boundary: - You may contact the npm registry, to download the named package. - Do not push, publish, or sync anything outward. Sending a vault out is a separate decision I make later. When you finish, tell me what each step changed or created, include the paths, and say which steps made no changes.
Nothing is published by any of these steps. Sending a vault outward is a separate, explicit decision you make later.
Step 3 does double duty: alongside your local setup it installs Lyt's operating manual and skills into your agent's own instructions. From your next session onward you can just ask for what you want — no package names, no commands.
npm install -g @younndai/lytRequirements
Along with npm, which Node.js includes, these are the things Lyt needs on the machine.
- Node.js 20.9 or newer.
- Git, because each vault is a plain git repository.
- GitHub CLI authentication only when you want to sync, share, or use GitHub-backed discovery.
Verify the install
lyt --versionLyt prints the version it is running, which confirms the install. Run lyt help for the current command groups.
Keep it current
Checking for a newer Lyt is free and changes nothing; updating is a separate, confirmed step.
Check whether my Lyt install is current, and tell me what a newer version would change.
The check only reads the registry. Nothing on this machine changes.
lyt outdatedUsing Lyt, update it to the newest version on the latest channel, then tell me exactly what it installed. Start a fresh session afterwards so you pick up the new manual and skills.
The update asks for confirmation before it replaces the global install, then reconciles Lyt-owned integrations through the new binary.
lyt update --channel latest --yesLyt ships often, so it is worth asking now and then. An unreachable registry is not a failure — the check simply says so and moves on.
Next: Quickstart.