YOUR IDEA. A CLEAR NEXT STEP.

Say what you want to make. Give the work direction.

An idea can begin in a few spoken sentences. Sofa is being developed to connect that conversation with a useful brief, an agreed next step and a result you can inspect.

From an idea through a plan to a product.
VabesTap me — I’ll say hello.
Assistant direction

A conversation with somewhere to go.

A booking tool, a small website or a less repetitive workflow: start with the person it should help and the change you want to see. Sofa’s intended role is to organize that thought, ask useful questions and keep the emerging brief understandable. You can refine the wording before it becomes work.

Voice interaction should make its transcript and next action visible. Microphone access, a chosen voice service and associated costs need explicit setup. A friendly character does not provide permission to record, send project data or start an agent.

Good questions make a smaller first step.

Who will use it? What should they accomplish first? Which example would show that it works? Separate an essential first version from attractive later additions. Capture assumptions, unresolved choices and observable acceptance checks. The brief remains yours to edit.

Current building blocks

Ground the conversation in the work.

The current local implementation brings configured projects, agent states, owner decisions and recorded results together. Managed Codex execution is supported; other tools depend on an import path and adapter. The complete spoken-request-to-architect workflow remains a development direction. Availability depends on the build.

Stay involved where your judgment matters.

Agree the goal, the files and actions in scope, the checks and the stopping point. Review a meaningful plan before a larger change. Answer choices that affect the product, access, spending, production or data. An architect handoff keeps a question moving through the process; it does not turn an unanswered owner decision into approval.

Bounded unattended work means an agreed queue can proceed within its permissions and limits. It stops for a required decision, a block or its agreed boundary. You need not watch every routine step, and a changed requirement can return to the plan.

Come back to something you can assess.

Review the change, relevant checks and remaining uncertainty. A recorded result is evidence to inspect; acceptance belongs to your process. Request a focused correction or choose the next useful increment. Use the Vabes method or your own documents.

This page explains the intended assistant experience. It does not announce a shipped whole-app voice builder, a complete commercial installer or guaranteed autonomous delivery.

Eight characters. One team.

Character in every movement.

Find a familiar face. Then meet the character behind it.

Your companion

Vabes

Architecture and product

2D character

01 · Your choice

The main team

Three younger companions

Meet Vabes ↓
A little movement and personality

Mood

Little signals

02 · A little closer

Meet Vabes.

Character & specialty

Chief architect

Architecture and product

Product architecturePlans and specificationsPriorities and decisions

Big idea first. A good plan next.

Legend says Vabes once planned a birdhouse so thoroughly that it acquired its own roadmap. Now he catches big ideas mid-flight and always asks what the finished thing should actually do.

A proper hello

I’m Vabes. Tell me your idea. Let’s start with a good plan, rather than seventeen buttons.

A short introduction, just for you.

Your companion

Vabes

Choose the character you would like to have by your side. You can change your mind any time.

Saved in this browser on the Vabes website. Choose your app companion separately in Vabes settings.