Lily is not Claude Code for non-developers.
It's a new Office designed for knowledge workers.

Design for office work — not from a developer's perspective.

Different design origins lead to different products

Claude Cowork

  • Built from Claude Code
  • Developer-first foundation
  • Expanded to non-coding tasks
  • File- and folder-centric

Lily

  • Designed from office work itself
  • White-collar mental model first
  • Workflows, tasks, outcomes
  • The beginning of a new Office

Designed for how office work actually gets done

Work starts with goals, not commands

Safety, review, and control are default

No Terminal, no Prompt, no API thinking

Users delegate work instead of "telling tools what to do"

Different interaction models

Claude Cowork

1

Give access to a folder

2

Assign tasks

3

Watch execution

Inspired by agentic CLI workflows

Lily

1

A visual work desk

2

Assign tasks to digital workers

3

Observe, intervene, approve, reuse

Inspired by how managers work with teams

From skills to work menus

Cowork provides an initial set of skills

Lily treats Skills as office work menus

Users choose what they want done

Lily decides how it gets done

No prompting. No learning curve. No configuration.

Why Lily exists alongside Claude Cowork

Models will not unify into one

Compute abstraction remains valuable

Office UX is a taste problem, not a model problem

New Offices are not built by simplifying developer tools

Claude Cowork extends Claude Code.
Lily rethinks office work.

Lily is where AI collaborators work alongside you, every day, to get things done.

Ready to experience the new Office?

Lily is not Claude Code for non-developers. | Lily