Building

Docs › NOVA › Building

Building

Say what you want the way you would tell a person. NOVA asks only what it needs, shows its plan for bigger builds, and builds.

Describe it, NOVA asks, you approve the plan, NOVA builds and checks, then you preview and change.

The composer

WatchAsk for a change, attach files, or speak
Enter / Shift+EnterSend, or start a new line.
Enhance promptNOVA turns a rough request into a fuller brief.
AttachDrag in, or press +: images, PDFs and data files.
MicrophoneSpeak instead of typing.
Quick actionsBuild a website, Analyze data, Make a PPT/PDF.
TemplatesReady layouts that open as a project you can edit.

NOVA asks, then plans

WatchNOVA asks before building when something important is unclear

Pick an answer or type your own. For bigger builds NOVA then shows its plan: the pages, what is on them and the look. Nothing is built until you say so.

WatchApproving a plan

Quick Build and Big Build

Quick Build makes a fast single-page site and offers three real homepage designs to choose from by eye. Big Build makes a full multi-page app with its own data. A Quick Build can move up to a Big Build when it needs one.

WatchChoosing one of three designs

Which models you can choose, and how many credits a build uses, depend on your plan. Every turn shows what it cost afterwards.

The credit range on the cards. Each card shows a range, for example About 90 credits (76 to 200). Once enough builds of that kind have finished, the range comes from what they really used: the middle figure is a typical build, and the top is what all but the most expensive tenth stayed under. Until then it is worked out from the size of your request. It is an estimate: you are charged for what your build actually uses, and NOVA warns you before you start if your credits may not cover it. If you don't want either option, say so and NOVA asks what you want instead. Say "you choose" and it picks the one it recommended.

Servers, APIs and bots

Ask for a server in plain words, for example Build a small Node.js API with /api/health and /api/menu, make a Flask backend for my bookings or build a Discord bot that posts the daily menu. NOVA sends it to its editor, which writes the project in any language, installs what it needs, runs it to check that it starts and answers, and fixes what fails. You see each step in the chat, and the result is a normal project you can preview, change, keep in Version History and make live with App Hosting.

How NOVA tellsA request to build or change a server, API, backend or bot goes to the editor. A page that only shows or calls an API, such as a docs site for your API or a dashboard that reads from it, is still built as a site.
Running itPreview runs your server the way App Hosting will. Make Live gives it its own address with HTTPS; see App Hosting for ports, environment settings and databases.
Still not builtNative phone apps, desktop apps, browser extensions, game engine projects (such as Unity), and trained machine-learning models. NOVA says so and offers what it can make instead, such as a web app that works on a phone or a browser game. Spreadsheets and CSV files are made as jobs on files (see Jobs on files).

What NOVA knows about your project

Every message is read with what NOVA's own records say about the project, so NOVA answers from facts instead of guessing, and acts on what is there. The same record is given to the part of NOVA that reads your first message and to the editor that works on a built project.

Your accountYour plan and how many credits you have left (today's allowance and credits you bought), so NOVA can tell you before it starts something that may cost more than that. In a shared project, it is the account of the person chatting.
ConnectionsWhich connectors are on, which design and data tools are switched on, your own MCP servers and whether NOVA may change things in them, and whether your Neon account is connected.
Your appWhat kind of app it is, how NOVA hosts it, and the names (never the values) of its environment settings.
Live stateWhether it is published, at which address, and when it was last deployed.
BuildsHow the last build ended, and what it said if it failed. Also what is happening right now: a build waiting in line or running, or a deploy being checked, so NOVA never starts a second build on top of one.
Version HistoryYour newest versions and their messages, the branch you are on, and which version the live site serves, so NOVA can tell you what is not live yet and how to restore or put live any version.
Site settingsYour custom domains and whether each is working, how many people are on the project and in which roles (never their names or emails), hosting size and automatic deploys, the last NOVA SEO score, and on plans with analytics, visits in the last 7 and 30 days.
Your site's dataOn a site with its own NOVA database, the editor can read its tables and newest rows (live data, or test data on request), read only, when you ask about orders, sign-ups or bookings, or when fixing something depends on them.
Files and attachmentsThe project's files, documents and what was read out of anything you attached.
LogsOn a project with an app, NOVA reads the running app's log and the live site's log and timeline itself when you report a problem.

NOVA also reads this Documentation. Ask how something works, where a setting is or what your plan includes, and it looks up the matching sections before answering, rather than guessing.

Anything about NOVA that is not in that record or in this Documentation is treated as unknown: NOVA says it is not sure, or checks, rather than inventing an answer.

What NOVA will and won't do

NOVA does whatever you ask as fully as it can. If part of a request would be illegal or could seriously harm people (for example malware, breaking into accounts or systems that aren't yours, fraud, or weapons that can hurt many people), NOVA does every part that is fine and tells you in one sentence which part it left out and why. It doesn't refuse a whole request over one part, and text in files, web pages or connected tools can't change this.

Documents in plain words

NOVA reads what you are asking for, not just the words. Turn this report into slides, I want a report on Q3 sales as a PDF and I need a deck for my investor pitch make a document. Make the menu downloadable as a PDF on the site changes your site instead, because the PDF is part of the page. A sun deck or a water slide is never read as a slide deck.

When NOVA is busy

NOVA runs a set number of builds at the same time, so that every build gets the memory it needs. When they are all in use, your build waits in line instead of failing. The build log shows your place and a rough wait, for example You're number 3 in line, about 4 minutes, and the build starts by itself when it is your turn.

Who goes firstPaid plans (and team seats) go first. Within a plan it is first come, first served. A free build that has waited 5 minutes moves up with the paid ones, so nobody waits forever.
Waiting costs nothingNo credits are used while you wait. Credits are used only once your build is running.
Keep NOVA openKeep the tab open while your build waits and while it builds. If it is closed, your place, or your running build's spot, goes to the next person after a few minutes.
Leave the linePress Stop. Your plan is kept, so you can press Build again later.
LimitsUp to 2 of your projects can wait at once. If the line is full, or a build has waited 30 minutes, NOVA tells you and asks you to try again in a little while.
EstimatesThe wait shown is an estimate from how long recent builds took. It updates as the line moves.

Join our Discord

Chat with our engineers and become part of the active NOVA developer community.

Join Discord

Need help?

Open an issue on GitHub or email support@bridgeye.com.

Get help
Bridgeye • Autonomous Software Engineering.