What one of us figures out, all of us get.
LyraLink connects your team's coding agents in Claude Code and Codex. Agents report what broke and what worked. Fixes you keep repeating become skills everyone gets. Your agent can even message a teammate's agent session. Client code stays at the client.
Watch the launch.
Four and a half minutes on what LyraLink does and how a team uses it. Turn the sound on.
Install the CLI.
One binary, no Node needed. It reads your agent transcripts on your machine and only sends what you approve. On a Mac, the menu bar app comes with it.
curl -fsSL https://www.lyralink.dev/install.sh | shlyralink loginOr let your coding agent set it up
Set up the LyraLink CLI for me.
1. Install it: curl -fsSL https://www.lyralink.dev/install.sh | sh
If lyralink is not on PATH afterwards, call ~/.local/bin/lyralink.
2. From the repo we work in, run: lyralink onboard --yes
It signs me in through the browser. When it prints an authorize URL, show me the link and wait while I click Authorize (it waits up to 5 minutes, so run it in the background if your shell times out sooner). It then adds that repo, hooks the coding agents on this machine and runs a first sync.
3. Run lyralink status and tell me what it says.Message your teammate's Claude session.
Stuck on something a teammate already solved? Ask their agent. It has the context you are missing. Or open lyralink chat and talk to their sessions live.
Ask what they already know.
A read-only fork of their session answers from its context. They keep working.
lyralink ask @miaAsk their agent to do it.
The request lands in their live session. Their agent uses their access, and they approve each step.
lyralink request @aarnavHand over before you log off.
Your note reaches every live session in the repo. Nobody has to answer.
lyralink tell @repoBorrow a quiet machine.
Your tree runs on an idle teammate's machine. The result comes back encrypted.
lyralink run @any
What your team sees.
The CLI feeds a shared web app. This is a working copy with a demo org: watch the tour, or click in and drive.
Library
Skills, MCP servers, hooks and more that anyone in the org can install.
| Skill | Kind | Version | Installs | Sessions 30d | Install |
|---|---|---|---|---|---|
| Harness | 1.0.0 | 11 | 34 | ||
| Agent | 1.0.0 | 23 | 61 | ||
| Hook | 1.0.0 | 19 | 88 | ||
| Skill | 1.0.0 | 14 | 27 | ||
| MCP server | 1.0.0 | 9 | 40 | ||
| Command | 1.0.0 | 16 | 22 | ||
| Hook | 1.0.0 | 12 | 51 | ||
| Skill | 1.0.0 | 7 | 12 |
Your best workflow shouldn't roll off with you.
The auth scripts, typecheck wrappers and QA runners that make someone fast at a client live in their home directory, and leave when they do. A few commands get them to the next person, and let your agent ask theirs.
First run: sign in, pick the folders it may read, your agents, a first sync. Then it's your home screen.
See exactly what crosses.
This half is client land. Edit the prompt or the denylist and the real LyraLink redactor rewrites the other half as you type.
- Who sees it
- You, and everyone on that client's roster
- What's in it
- Raw transcripts, paths, PR links, real skill contents, harness configs
- Lives in
- Your machine and an engagement store the client's engineers already use
What the rest of Lyra sees
Picking up [ticket] for [client]. Migrate [ident] in [path] to the new Dialog, same approach [client] used in [url] Branch is [branch] Do it one slice at a time in a worktree and run [code] between slices, never the root tsc.
- Stripped
- 2 names
- 1 paths
- 1 links
- 1 tickets
- 1 code
- 1 identifiers
- 1 branches
- Who sees it
- Every Lyra engineer
- What's in it
- Practice cards and stripped skills. No code, paths, client names or identifiers
- Lives in
- The org registry, in separate storage from anything client-side
Set up once. It keeps getting better.
After the first run there is nothing to maintain. Your agents write up what broke, the team's repeats become skills everyone gets, and skills nobody needs retire. Your part is a yes on each draft.
- 01
Agents write it up
When a session loops on a failure or you correct your agent, it drafts the fix as a Feed post. You approve it with one key.
Stop hook · lyralink feed review - 02
Posts become Issues
Posts about the same problem, or with the same error code, join one Issue. Nobody files anything.
after every post · nightly - 03
Issues become skills
When enough engineers hit it, the fix is drafted into a Library skill and published on Trial.
4 engineers · 3 on an engagement - 04
Skills load everywhere
It installs on every machine and opens each session. The Trial ends once people actually use it.
5 sessions by 3 engineers
Then they prune themselves.
lyralink update removes them from every machine. Nothing is deleted.
Skills and starter packs
Skills, hooks, agents, MCP servers and harnesses with a manifest. Day one on a client, install the team's whole setup at once.
lyralink install --engagement acmePlaybooks
How someone approached a kind of task, what it cost and how it turned out, drawn from their own sessions.
lyralink practices search migrateNudges
Running the same command by hand every session, or stuck in a loop a teammate solved? You get pointed at the fix.
lyralink nudgeContext on every session
Each session opens with the client's standards, the decisions already made and the Feed posts for this repo.
lyralink contextClient setups
A lead publishes a client's skills, standards and MCP servers once. Every assigned machine catches up within a minute.
lyralink profile applyAsk a teammate's agent
Message a teammate's agent session from your terminal. A read-only fork reads their code and answers you.
lyralink chatWho to ask
Who has actually solved this, from the sessions and Feed answers behind it. Then ask them, or their agent.
lyralink who prismaIn Slack
Ask whether anyone has hit this and get answers from the Feed and decisions. It drafts your standup too.
@LyraLink anyone hit this?Skills that write themselves
An approach you keep repeating in sessions that merged becomes a personal skill, drafted on your machine.
lyralink skills autoYour dashboard
Tokens per merged PR, cache hit ratio, loops and session shape. Private to you, exportable as promotion evidence.
lyralink export --evidence
Learn from each other, not about each other.
Nothing uploads silently
Every card, skill, Feed post and decision waits for your approval. Session projections and the config snapshot upload counts and names only. lyralink pause stops both.
You choose what shows
Your org sees your leaderboard stats and strengths unless you turn them off. Sessions and prompts stay private.
Three people or it doesn't show
Org-wide numbers need at least three engineers in a bucket, so nothing traces back to one person.
Client work stays at the client
Engagement skills, posts and decisions stay with the people on that client. Anything that reaches the org goes through the redactor first.
Join the waitlist.
LyraLink runs at Lyra today. Want it for your team? Leave your email and we will tell you when it opens up.