Graview Cloud for a bug bash
Twenty people clicking through the launch build for an hour. Each issue gets an area, a severity and the steps to reproduce it, and the list updates on every screen as issues are filed. A blocker with no owner stays flagged until someone takes it.
For the engineer running the launch bug bash, and the dozen people who'll find things for an afternoon.
Graviewacme.graview.app/a/launch-bug-bash
Live
You, in ChatGPT
Run a bug bash for our launch: what's broken, which area, how bad, and who's on it.
graview · create_app3 kinds · 10 records · 2 rules
Issues4
Areas3
People3
RuleCard payment spins forever is a blocker and nobody owns it
Rules2 of 2 hold
Watch it again
Sound familiar?
“Three people reported the same bug in three places.”
“Is that one bad enough to block? Who decides?”
“It was found at ten. Nobody owned it until four.”
For a bug bash
Issues with severity, steps and area
Owners, and what's been fixed
A live list the whole room works from
A week with it
you open the bash: areas, severities, who's on what; everyone gets the link.
findings land with an area and a severity; a blocker with no owner is flagged within the minute.
what's fixed, what's open by severity, and who's carrying the most; the launch call writes itself.
Templates
It's a complete app for a bug bash. Answer the questions it asks and it's yours to change. Or skip it and describe the job in your own words.
A punch list of what's broken, where, how bad, and whose it is.
How it works
There is no setup. The app's shape comes from what you describe, and it changes when the job does.
Add Graview to ChatGPT or Claude once. Then say what you're organizing, in your own words. Or start from one of our templates on graview.cloud.
You: “Track our kitchen renovation and what's on order.”How to connectAbout a minute later it's live at its own address on graview.app, with the records and rules the job needs. It shows up in your chat and opens on any phone.
okafor.graview.app/a/kitchen-renovationGive each person a role: owner, editor, viewer, or one your app defines. Everyone sees each change as it lands, with the name of whoever made it, your AI included.
Here now: Nick, Sam and AnaAsk for a deposit field or a budget warning and the app changes shape. Every record comes through. If one wouldn't, you're asked first, and earlier versions can be restored.
You: “Add a deposit field.” → version 2Privacy
People put real money and real addresses into these apps. This is who can see them, and what happens when you leave.
Only you can open a new app. Each person you invite gets a role: owner, editor or viewer.
A connected chat can do what you could do in that app, and nothing more. Its changes are labeled as its own, and it can never change who has access.
An app can keep some records to some people. A record you can't see is absent everywhere: on the page, in search, and in your chat.
Each app runs on its own, with its own storage, at its own address.
We don't read your apps or train AI models on them. Staff can look only if you grant support access: read-only, for 24 hours, ended whenever you like.
Export a whole app with its history at any time. Delete it and it's gone within 7 days, and from backups within 30.
Questions
No. It's the afternoon's board; what survives goes to the tracker as a file or by hand, and the rest doesn't have to.
Yes, by link, with a role that reports and sees the board but can't change the areas or severities.
Other jobs
Private alpha
Graview Cloud is invite-only while we build it with its first people. Tell us what you'd make and we'll send an invite when there's room.
Coming soon
Your own apps, kept as long as you like and exportable at any time. Free while the alpha runs.
Coming soon
Everyone you share an app with, each in the role you give them.
Already have an invite?
Sign in to the private alpha