Every part of HEWA, and what it does today.

Eleven areas, in the order you meet them in the product. Each line is one thing you can open and use now, with what it is for.

A project open in HEWA in a Chrome tab: file tree, editor, terminal and the agent panel after a finished build. Figures in the drawing are illustrative.

01Editor and files

Editor and files

A code editor with a file tree, project search, quick open and inline autocomplete, in a browser tab. On a phone the layout rearranges itself for a thumb and a small screen.

  • Browser code editor (Monaco)Write and edit real code in the browser with nothing to install.
  • File tree with create, rename, duplicate, deleteOrganise your project files the way you would on a laptop.
  • Project-wide search and replaceFind anything across your whole project in one place.
  • Quick open files (Cmd+P)Jump to any file by typing part of its name.
  • Code intelligence (Monaco TypeScript worker plus server symbol lookup)Autocomplete, hover and go-to-symbol while you type.
  • Inline tab autocomplete (HEWA Instant)Finish lines of code with one keypress, even on a slow connection.
  • Command palette (Cmd+K)Reach every action from the keyboard.
  • Git panel (status, stage, commit, branches, diff, log, pull)See your changes, branches and history without leaving the browser.
  • Mobile layout and keyboard barBuild from your phone when that is the computer you have.

02Terminal and runtime

Terminal and runtime

npm and shell commands run inside the tab in Chrome and Edge. When your own device is weak, a cloud sandbox gives the project a real Linux shell instead.

  • In-browser terminal (WebContainer, Chrome and Edge)Run npm and shell commands right in the browser tab.
  • Cloud sandbox terminal (server runner)A real Linux shell for your project when your own device is weak.

HEWA runs in Chrome and Edge on a laptop or desktop; on an Android phone, the editor, agent and preview in Chrome. In Safari and on iOS you can edit, build, preview and export; the live terminal is not available there.

03The build agent

The build agent

Describe what you want. The agent writes a plan, then the files. In chat, the agent proposes commands and waits for a yes. A build writes its files, installs and previews; every file it wrote can be undone with one click. Stop it whenever you like.

shop-mpesa in Agent mode on HEWA Smart: the prompt, the plan with its price, the files it wrote with Keep and Undo, the terminal and the preview.
  • Composer modes: Ask, Agent, Plan, DebugChoose whether the agent talks, plans, builds or debugs.
  • Plan first, then approve and executeSee the steps before any code is written, then say go.
  • AI build agent (Agent mode writes files)Describe the app you want and watch the files appear.
  • Live preview of the built appSee your app running the moment the agent finishes.
  • Self-fix after a failed installIf dependencies fail to install, the agent tries to repair the setup once.
  • Stop button; no charge if stopped before output completesChange your mind mid-build and you do not pay for what you stopped early.
  • Keep / Undo for an applied agent editRoll back an edit you do not like with one click.
  • Review and accept/reject proposed edits (per file and per hunk)Approve each change before it lands in your files.
  • Approve, edit or reject commands the agent wants to runNothing runs in your project until you say yes.
  • Agent Run panel (server-side multi-step agent loop)Hand the agent a goal and let it read, run and edit until it is done.
  • Server-side checkpoints with one-click restoreGo back to how the project was before the agent touched it.
  • Review a whole agent run as one changesetAccept or reject everything the agent did in one review.
  • Continue a stopped runPick up where the agent stopped.
  • Background agents / job queueLeave the agent working while you do something else.
  • Inline edit in the editor (Cmd+K on a selection)Highlight some code and tell the agent how to change it.
  • Fix with HEWA from a diagnosticTurn a red squiggle into a fix with one click.
  • Paste an image into chatShow the agent a screenshot or a sketch instead of describing it.
  • Web search in chat (@web)Let the agent look things up on the web when it needs to.
  • Saved chat history per projectCome back to any earlier conversation with the agent.
  • Custom MCP servers in the IDEPlug your own tools into the agent.

04Context

Context

Point the agent at exactly what it should read: a file, a folder, a web page, or the rules you wrote for the project.

  • @-mentions in chat (@file, @folder, @web)Point the agent at exactly the files it should read.
  • Pin files as contextKeep important files in the agent's view.
  • Codebase-aware chat (indexing + retrieval)Ask questions about your own code and get answers that fit it.
  • Project rules file (.hewa/rules.md or AGENTS.md)Tell the agent your project's conventions once and it follows them.
  • @docs and @git mentionsPull in docs and git history as context.
  • Auto-context from the active fileThe agent already knows which file you are looking at.

05Preview and sharing

Preview and sharing

The running app opens beside the code the moment the agent finishes.

  • Live preview of the built appSee your app running the moment the agent finishes.
  • Shareable preview links on an isolated preview domainSend a friend a link to try what you built.

06Bring your code

Built it somewhere else? Finish it in HEWA.

Import a public repository by URL, or open a folder from your computer. Your project can leave as a zip file at any time.

  • Import a public GitHub/GitLab/Bitbucket repo by URLStart from code you already wrote somewhere else.
  • Open a local folder (File System Access API)Bring a project from your computer into HEWA in a couple of clicks.
  • Download project as zipTake your whole project with you as a zip file at any time.
  • Connect GitHub account (OAuth)Link your GitHub account to work with private repos.
  • Push to GitHub from HEWASend your work back to GitHub when you are done.

07AI models

Models

Seven tiers, named for the job they do rather than for who makes them. Each has a flat credit cost per request.

Model tiers: HEWA Smart, Fast, Africa, Long, General, Pro, ReasonPick the model that fits the job and see what it costs before you send.

Credits per request, charged flat whatever the length of the answer

HEWA Smart
1 credit per request Coding-heavy tasks and refactors; the default for building.
HEWA Fast
1 credit per request Quick answers and everyday help.
HEWA Africa
1 credit per request Prompts in Arabic, Swahili, Hausa and other languages.
HEWA Long
1 credit per request Large codebases and long documents.
HEWA General
1 credit per request A balanced everyday model.
HEWA Reason
3 credits per request Deep problem-solving and long reasoning chains.
HEWA Pro
5 credits per request The most capable tier, for complex tasks.
  • Credit cost shown per tier before you sendKnow the price of a request before you run it.
  • Suggested-tier chipGet a hint when a cheaper or better tier would suit your prompt.
  • Vendor and model names are not shown by defaultPro accounts can reveal which vendor and model answered a request.
  • HEWA Offline (browser-local model)Keep coding with a model in your browser when the network drops.
  • HEWA Private (connect your own model / Ollama)Run HEWA against a model your company hosts.

08Planning

Planning

Choose how the agent works before you type, and see the steps before any code is written.

  • Plan first, then approve and executeSee the steps before any code is written, then say go.
  • Composer modes: Ask, Agent, Plan, DebugChoose whether the agent talks, plans, builds or debugs.

The four modes in the composer

Ask
The agent answers Questions about your code. Proposed commands wait for a yes; nothing is written to your files.
Plan
The agent plans Lists the steps first and waits for you to say go.
Agent
The agent builds Writes its files, installs and previews; every file it wrote can be undone with one click.
Debug
The agent debugs Works through an error with you.

09Deploy and data

Deploy and data

Put the app online, give it a database and keep API keys out of your code and out of the chat.

  • One-click deploy on HEWA hostingPut your app online with one click.
  • Provisioned Postgres database per projectGet a real database for your app without setting one up.
  • Project secrets (env values stored server-side)Keep API keys out of your code and out of the chat.

10Teams

Teams

Invite people to the same project and give each of them a role.

  • Teams / organisations with roles and invitesWork on the same project with your team.
  • Shared organisation credit walletOne wallet your whole team draws from.

11Account and safety

Account and safety

Sign in the way you already do, add a second lock to the account, and get a short guided start.

  • Sign in with email/password, Google or GitHubSign in the way you already do.
  • Two-factor sign-in (TOTP)Add a second lock to your account.
  • Password reset by email linkGet back in if you forget your password.
  • Onboarding overlay and Getting Started checklistA short guided start so the first build is not confusing.

Start with one prompt

Open a tab, describe the app, and watch the plan appear. No install, nothing to download.