TellWang
Dashboard
Core concepts / How Wang works

How Wang works

You onboard Wang as your AI employee — your CTO hire. Tell it what you need in plain words and it builds and runs your Wok for you: it sets up the database, auth, storage, realtime, functions, scheduler, email, SMS, hosting, the built-in AI model, and key management, then builds your app on top, checks each part actually works, and gives you something live. You own what comes out — the features, the code, the look of the software that runs your business. Wang builds against a live Wok throughout the process, so what you get back has already been provisioned, deployed, and tested on the real system you'll use.

✦
Build now — open the dashboard and start a chat. Tell Wang what you want and it builds in the page, streaming as it works. Free includes DeepSeek Flash and one hosted run at a time.
✦
Most tools hand you the parts and leave you to wire them together and put them online — and things break in the gaps. Wang does the whole job and checks it works before handing it over, so you don't get "it worked on my screen but broke when it went live."

How Wang builds your Wok

Every change — whether you asked for it or Wang did it — goes through the same four steps on your real Wok:

  1. Work on the real thing — Wang changes your actual Wok, not a draft or a guess.
  2. Build it — sets up the data, the rules, the automations and the app.
  3. Try it — Wang runs the project's test, lint, typecheck, and build scripts plus targeted runtime checks for the change. It can open the app in a real browser when that helps diagnose visual, console, or network behavior.
  4. Publish and finish — Wang shows you the exact Preview and test summary. Publishing starts only after you approve that Preview, and the release rechecks its exact source, artifact, context, and manifest pins before changing Published.

Because Wang tests on the real, running Wok, the classic "it worked while I was building it but broke when it went live" problem doesn't happen.

✦
Selling, built in — payment is pre-integrated, so anything Wang builds across your funnel can take money without you wiring up a processor. Fill in a little basic info to take your first $600 by card, then a quick KYC/KYB check when you're ready to withdraw.

What Wang can actually do

Ask in plain words and Wang takes the action — set up a Wok, change your database, deploy code, schedule recurring jobs, add logins, register and wire up a domain, put your site online, send and read email, search what you've taught it, top up credits, and connect Slack or Telegram. Developers can drive the same actions directly over the API.

Inside an app workspace, Split opens the running app beside Wang. Desktop keeps a 1280-pixel layout viewport and scales it to fit, while Mobile uses a phone viewport. Starting Annotate gives the preview the full detail area so individual elements are large enough to select.

Teach Wang about your business

Onboarding is a conversation: Wang wants to understand where your business is now, where you want it to go, and the end goal. Every current plan can chat with Wang directly in the dashboard; Free uses DeepSeek Flash and its included monthly model allowance. What you teach Wang applies wherever it runs:

Your instructions and knowledge base apply everywhere Wang runs — the dashboard chat and the Slack/Telegram channels — so the whole team gets the same context-aware Wang; your design system applies whenever it builds a frontend. Chats live at the organization level rather than inside one Wok. A focused Wok is an optional starting point, and Wang can still work across several Woks because each action names and authorizes its target explicitly. Every organization gets its own Agent Cell. Each active chat gets an isolated worker whose access is bound to the human who started it, while TellWang keeps identity, approvals, tools, audit, and the conversation in one place.

Picks up where you left off

App building in Wang uses a coding model. Free organizations can select DeepSeek Flash; paid organizations can also select DeepSeek Pro or Kimi, and any member can connect ChatGPT or Grok. The composer keeps the message unsent until a coding model is selected. The Private model is available to developers through the model gateway.

While Wang works, the chat shows verified lifecycle state and a safe ledger of the files, releases, and checks its tools touched. Wang's reasoning appears in a collapsed Thinking panel; its replies appear as ordinary Wang messages outside it. The working stopwatch remains visible beside the run. Each independently accepted final answer stays a separate immutable message. Opening a chat under a project opens its app Preview beside the conversation automatically; closing Preview still leaves it closed until another project chat is opened. The capability matrix above the Agent Cell composer attaches the selected capability behind the scenes for app creation, domains, email, RAG, functions, automations, diagnosis, and other common work. The composer and durable user message stay exactly as the user wrote them. Click an active capability again to deselect it. The composer accepts one PNG, JPEG, or WebP screenshot through its upload control or a clipboard paste. A compact cue beside Send shows Ctrl ↵ on Windows and Linux or ⌘ ↵ on macOS; plain Enter remains available for multiline messages. Wang chat's model row has one DeepSeek pill: Free can select Flash, while paid plans also see Pro. It also lists paid-plan Kimi, personal ChatGPT, and Grok Build through a member's Grok or SuperGrok subscription. Both personal connections use device sign-in; TellWang never asks for an xAI API key. For Wok-focused work, Wang works in the named app's Preview checkout. Static files follow the browser route: frontend/index.html is /, while frontend/<route>/index.html is /<route>/, so two index files are separate pages rather than duplicate checkouts. Root-page requests start at the root file; site-wide work also inspects shared assets and every routed page that owns the repeated UI. Wang follows that checkout's AGENTS.md and TELLWANG.md. TellWang checks the final answer against your request and the run's evidence before marking it complete. The conversation, queue, active run, typed model streams, safe progress, and execution stopwatch survive a refresh. Team members can submit attributed follow-ups while Wang is busy and share a private group chat without filing a cross-Wok task under the first app it touches.

When only DNS propagation remains, Wang finishes and marks the domain as pending activation. A domain whose DNS still needs your action stays open until you make the change.

One Wang, every channel

Connect a Telegram or Slack bot through the channel API so your team can message Wang from the chat app they already use. Engineers drive the same Wok over MCP or the REST API; the dashboard shows the connection address and prepares a scoped prompt.

Confirmation & guardrails

Wang handles safe, undoable work on its own, but asks first before anything risky — deleting data, buying a domain, sending email, spending money. And it can only ever touch your team's own Wok — never another team's, even if someone tries to trick it into it.

Portable by default

A Wok is yours to take. Your data is plain Postgres you can pg_dump on any plan, so it's always yours. On every paid plan, a Wok's entire definition — schema, policies, functions, env, storage config, scheduled jobs, and infra shape — also exports to Terraform HCL in one call:

export.sh
curl https://tellwang.com/v1/woks/$WOK/terraform \
  -H "Authorization: Bearer $TELLWANG_KEY" > wok.tf

terraform init && terraform apply
# → redeploys this Wok on a different cloud, your own account, or self-hosted.

No lock-in: TellWang earns its keep by running your Wok well, not by trapping it.

Proven in practice

We built a full point-of-sale system this way first, and building on the live system beat writing code and deploying it separately every time. TellWang is that, packaged for your team.