LVLZ has two ways in. You can text your agent, or you can open the workspace at app.lvlz.ai. We made a rule early: anything you can do in one, you can do in the other. This post explains how we keep that promise without relying on memory and good intentions.
Why parity matters
If the app can archive a project but the agent cannot, you learn not to ask the agent. If the agent can set up a routine but the app cannot show it, you stop trusting the app. Each gap teaches you to work around the product. Parity means you never have to wonder which side can do what.
One definition per capability
Every operation, such as creating a task, sending an email or starting a browser task, is defined once in a shared registry. A definition holds:
- a stable key, like
task.create, - a typed schema for its input,
- how it is gated (whether it needs your approval),
- which surfaces offer it,
- an example of how you would ask for it in plain words.
From that one definition we generate the tool the agent calls, the HTTP endpoint the app calls and the entry in a manifest. The same handler serves the agent and the app, so the behavior is identical by construction.
A check that fails the build
Definitions alone don’t guarantee parity, because someone still has to implement each side. So our build runs a parity check. If a capability is marked live but one side has not implemented one of its operations, the build fails. If an operation is implemented on every side but still marked as coming soon, the build fails too, so the public status cannot lag behind reality.
The website reads the same list
The manifest also feeds this website. The features page and every page under it list each capability with its status, Live, Soon or Later, and where it runs: the app, iMessage or WhatsApp. When we ship something, the page updates on the next deploy. When we write that something is coming, it is because the registry says so.
What it means for you
You can learn LVLZ once. Whatever you find in the app, you can ask for by text, and whatever the agent does, you will find in the app. And when you read our feature list, you are reading the code.