No forms. Just talk.

No forms. No settings panels. You just talk.

Most software is configuration screens dressed up as features. You open a settings panel, look at thirty checkboxes whose meaning is half-clear at best, and try to predict your future behaviour well enough to choose the right ones. Then you give up and accept the defaults.

1Presence does not do that. There are no settings panels. There is one screen and it is a conversation. Want a new agent? Tell Presence what you need. Want a recurring workflow? Describe the pattern. Want a different tone of voice? Say so.

This is not a limitation we apologise for. It is the design.

When you describe what you want in plain words, Presence 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. Presence handles the craft.

What it looks like in practice:

"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, in plain English, that you can rewrite.

The conversation is the front door. The full structure is always behind it, browsable if you want it. Most people never need to look. The ones who do can read every word, edit anything, and watch the changes take effect on the next turn.

• It is faster. Describing what you want takes thirty seconds. Building it in a settings panel takes twenty minutes.
• 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.