AI-built apps

Built by an agent, checked on the live app

Claude Code, Codex, Cursor and Copilot can ask Vraelis for a check before they report done. A person approves the plan; the answer goes back with a repair prompt.

Set up your agent See the record

The app: Notewell, built with Lovable
From one sentence: 2 journeys: the note survives sign-out, the dashboard stays private
The run: 18 steps in 17.4 s
Clean-up: The check deleted its own test note

From a run on Notewell, a Vraelis demo app, on July 31, 2026.4fc6e52cRead the record

The problem

Done is a claim, not a result

The agent checks what it wrote

Its tests come from the same reading of the task as its code. Vraelis starts from your sentence.

Done means it compiled

A green build says nothing about what a user can do on the deployed app.

The fix is reported, not checked

The re-check tool runs the same approved plan again and returns the new answer to the agent.

How it fits

The agent asks, and the answer comes back

Three MCP tools, local or hosted.

vraelis.com/mcpMCP tools

vraelis_verify
The agent asks for a check, with your sentence and the address of the live app.
403 plan_requires_human
A person approves the plan. An API key that tries gets this answer.
vraelis_status, vraelis_recheck
The answer goes back to the agent with a repair prompt, and the re-check runs after the fix.

A real check

The note was still there after signing back in

Notewell is a demo app built with Lovable. Vraelis wrote two journeys from one sentence, and the check cleaned up after itself.

Notewell

The plan Vraelis wrote from one sentence had two journeys: the note has to survive signing out and back in, and the dashboard must not open for someone who is signed out. The check deleted its own test note at the end.

Outcome: Did what the sentence says
Run ID: 4fc6e52c
Recorded: 2026-07-31
Duration: 17.4 s

Read the whole record

The sentence, the steps and the finding

A signed-in user can create a note and still see the same note after signing out and signing back in.

Create and persist a note across sign-out and sign-in

Open /auth1.3 s
Sign in as the test member3.2 s
Open /dashboard123 ms
Type “Test note title” into Title723 ms
Type “Test note body content” into the note225 ms
Click “Save note”342 ms
Check Your notes shows the title1.1 s
Check Your notes shows the body85 ms
Click “Sign out”340 ms
Check the address is /auth250 ms
Sign in as the test member again2.0 s
Open /dashboard103 ms
Check Your notes shows the title850 ms
Check Your notes shows the body86 ms
Click “Delete” to clean up the test note345 ms

Verify dashboard is gated without authentication

Start a fresh browser session82 ms
Open /dashboard while signed out114 ms
Check the address is /auth0 ms

Notewell's sign-in page, where the browser was sent after opening /dashboard while signed out.

Examples, the first was run on Notewell and is quoted as written; its plan also covered the second

“A signed-in user can create a note and still see the same note after signing out and signing back in.”
Signed out, opening /dashboard sends the browser to sign in.
A new visitor can sign up and reach the dashboard.
Uploading a profile photo shows the new photo after a reload.

It does not read your code, and native and desktop apps are not built yet.

Limitations