You say what you want. The writing gets written.
Where a conversation beats a form
Configuration screens dressed up as features: thirty checkboxes whose meaning is half-clear at best, and a request that you predict your future behaviour well enough to choose the right ones. Then you give up and accept the defaults.
1Presence draws the line differently. Anything that is really a piece of writing — an agent's identity, a skill, a workflow stage, a standing preference — is written by talking, because that is what it is. Want a new agent? Tell 1Presence what you need. Want a recurring workflow? Describe the pattern. Want a different tone of voice? Say so.
The switches stay switches. Speech settings, your language and currency, billing, connecting a service from a card in the chat — those are a tap where you would expect them, and that is the right shape for them. What you never do is describe a person in a form.
1Presence is an expert at this
When you describe what you want in plain words, 1Presence translates that into something precise and effective. The way a good director translates a vague brief into a casting decision. The way a good architect turns "I want light in the morning" into a specific window orientation.
Behind the scenes, it knows the craft: the right level of specificity, the right constraints, the right voice, the right structure. It writes identities that draw the best performance from the models underneath. It writes skills that trigger in the right moments. It assembles workflows that read like recipes, not flowcharts.
The result is agents and skills that work better than anything you would have built in a settings panel, because they were shaped by something that understands both you and the system at the same time.
You stay in the conversation. You describe intent. 1Presence handles the craft.
Examples
What it looks like in practice:
Creating an agent
"I want someone who sorts my inbox every morning — terse, decisive, no ceremony." 1Presence asks a couple of clarifying questions, then offers a card: Set up this agent. One tap, and it walks you through naming, voice, connectors and skills — and, if it should run on a schedule, sets that up too.
Building a skill
"Whenever I say 'prep me', check my next meeting, pull context from my vault, and write a one-page brief." 1Presence shapes the trigger, structures the steps, and saves it.
Adjusting behaviour
"From now on, default to bullet points." "Stop summarising at the end of every answer." "Be more sceptical when I describe my own ideas." Before a preference is kept, it shows you the exact words it would store, with Save and Not now — and saves only when you say so, for that agent.
Designing a workflow
"Every Monday morning, pull together a brief: weekend email, the week's calendar, my open GitHub issues. Let me read it before anything sends." 1Presence designs the stages, picks the agents, and sets the schedule. Each stage carries a one-sentence summary of what it does, and the workflow screen is made of them.
And the fastest setup of all is a Kit — agents, skills and routines for one corner of life, offered in a conversation with a “Set it up” card and installed with your tap, that lands you somewhere sensible the moment it is in. Browse the Kits.
In the conversation itself
Talking to it is built to feel like talking. Send a thought in pieces — three messages while you work something out — and it reads them as one, instead of answering the first alone. When it has a suggestion for what you might say next, the words sit in the composer as a placeholder; press Tab and they are yours. Write in Spanish and it answers in Spanish; the next English message comes back in English, with nothing to set.
A small ring beside the composer shows how much room the conversation has left. A long thread folds its older messages into a summary and leaves a mark where it did — "Compacted 24 messages" — that opens to show what was carried forward. When a conversation is filling up, it says so, once.
Ask for something that is really another agent's job and it offers to hand over — a card naming the agent, one tap to move the thread. Every agent knows who else you have, so the handoff is a real one, not a guess.
When you do want to see the details
"Conversational" does not mean "opaque." Every agent has a profile page where you can see and edit its identity, its skills, and what it can access. Every skill has its own detail page you can read. Every workflow is a list of stage cards, each with a one-sentence summary you can read at a glance.
The conversation is the front door. The full structure is always behind it, browsable if you want it — and where a page holds a piece of writing, the dark button on it (Edit Stage 02, Edit Routine, Edit your Agent) opens a chat that already knows what you are looking at. You read every word; you change it by saying what should change; it takes effect on the next turn.
Why it ends up better
- It is faster. Describing what you want is a sentence. Building it by hand is a form.
- It is more precise. Plain language carries nuance — "warm but not effusive" — that a checkbox cannot.
- It scales. Want a team of six agents with handoffs between them? You can describe that in a paragraph. You could not draw it.
- It evolves. "Iris has misread the same sender three times — update her skill" is one sentence. That is a real change you would otherwise never bother to make.
- It teaches you the product. The conversation surfaces what is possible. You learn by trying things in language you already speak.
The whole idea
The configuration screen is a conversation.
Agents, skills, workflows, behaviour — everything you would once have typed into a form, you say. You describe intent in plain words; 1Presence handles the craft. The switches stay switches; the writing gets written.
Start a conversation.
Free to try. No credit card. Just you and your agent.
Works on any device. Start chatting straight away.