The two things that do work
Assistant
Converses. Someone — or something — sends a message and gets an answer, in a conversation that persists. Real-time, embeddable, the natural fit for support, sales and any interface a person uses.
Agent
Executes. It is given a task and works through it in a thread: planning, calling tools, pausing for approval, finishing. Long-running, autonomous, the natural fit for processes.
The four things they use
The two things that organise it
Project
How work is divided inside your account: access, cost and traceability follow the project. See Projects.
Tenant
How work is divided outside it: your own customers, and the users inside them. See Multi-tenant.
These two are easy to confuse and are not the same axis. A project is your internal organisation — who on your team works on what. A tenant is your customer. A single project usually serves many tenants.
How they compose
A support assistant, embedded in your product:1
An assistant
with a prompt and a model.
2
Knowledge
attached — return policy, product catalogue, tone of voice.
3
Tools
from a connected app, so it can look up a real order.
4
Memory
scoped by subtenant, so it remembers each customer and only that customer.
5
Embedded
with
@devicai/ui, authenticated with a tenant session so the customer’s identity is proven rather than declared.1
An agent
with a plan and a schedule.
2
An environment
with the database CLI installed and the credentials as encrypted variables.
3
A sandbox snapshot
so each night starts where the last one left off.
4
Human in the loop
on the step that writes, so a person approves before anything moves.
5
A trigger
or a schedule, so nobody has to start it.
Three ways to reach all of it
Console
app.devic.ai — build, watch, review.
Public API
Everything the console does, and what your product calls.
CLI and SDK
The same API from a terminal or a Node backend.