livewithlively

Lively — AI skill for Claude Code

AI community

The agent OS where your team and its AI work from the same context.

How to install Lively

This entry records only its repository, not the path inside it, so there is no exact command to give. Open livewithlively/lively and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Lively does

The agent OS where your team and its AI work from the same context. Self-hosted, works with Claude Code, Codex and more · 팀과 AI가 같은 업무 맥락 위에서 일하는 에이전트 OS

Alternatives in AI

Multica — Make humans and AI agents work as one team — open-source and self-hostable 47.8k ★
Agent Teams AI — You're the boss, agents are your team 2k ★
Ante — Ghost in your shell 1.9k ★

README

Lively

**The agent OS where your team and its AI work from the same context.**

[![License: AGPL-3.0](https://img.shields.io/badge/license-AGPL--3.0-blue.svg)](LICENSING.md) [![Release](https://img.shields.io/github/v/release/livewithlively/lively)](https://github.com/livewithlively/lively/releases/latest)

[한국어](README.ko.md) · [Website](https://lvly.io) · [Managed (app.lvly.io)](https://app.lvly.io) · [Architecture](docs/architecture.md)

Lively has AI collect your team's documents, conversations, code, and decisions, keep only what is still true, and feed as much of it as needed to whichever AI each teammate uses (Claude Code, Codex, and others). On top of that context, agents do the work, and the apps your team builds read from the same context.

In an OS	In Lively
Memory	Context store: collection, duplicate and outdated-fact checks, injection. Session output flows back into the store
Processes & shell	Workspace: projects, tasks, and sessions that connect into one flow. Developers use the terminal; everyone else uses the web or desktop app
Apps	Apps: agents and tools your team builds run on the same context
Drivers	Integrations: Slack, Notion, GitHub, databases, and more

The core is open source under AGPL-3.0 and free to use with no limit on team size. If you'd rather not run a server yourself, use the [managed service](#dont-want-to-run-it-yourself-use-the-managed-service).

Why

Teams now use much the same models. The difference in results comes from whether the AI **knows your team's work**. Yet nobody is looking after that context.

You find things, but can't tell what's right. A two-year-old spec and last week's changed decision come back with equal weight, and the AI reads the old one and is confidently wrong.
What you organize goes stale. You build a wiki, and nobody keeps it up to date.
Work done with AI disappears when the session ends. A conclusion one person reached