Alpha feedback — how to report useful bugs on lattuce.app
How to report useful bugs on lattuce.app during alpha: page URL, steps, expected vs actual, and a screenshot. Do not send secrets.
Lattuce at lattuce.app is in alpha. Core research work is usable, and rough edges still show up. A useful bug report is short and specific: where you were, what you did, what you expected, what happened, and a screenshot when the screen is the evidence.
This guide is for authors and household members, not a runbook. For what “alpha” means day to day, start with Lattuce at lattuce.app is in alpha. Send reports through Contact.
Who this is for
| You are… | Send feedback when… |
|---|---|
| Trying Lattuce for a paper or thesis | A page errors, a file never becomes ready, or export looks wrong |
| Sharing the household account | Someone else cannot open a paper or library item you can see |
| Coming back after a quiet week | Something that worked last time now fails |
Questions about plans, privacy, or getting started can go to Contact or FAQ. This post is about bugs we can reproduce.
Before you start
| You need | Notes |
|---|---|
| The page that failed | Copy the full URL from the address bar on lattuce.app |
| One more try | Repeat the steps once so you know they still fail |
| A screenshot (when the screen shows it) | Crop to the error, empty state, or wrong result — not your whole desktop if you can avoid it |
| The Contact form | That is the public channel for alpha feedback |
You do not need a perfect write-up. You do need enough for someone else to follow the same path.
What to include
Use this list. Paste it into Contact and fill the blanks.
| Field | What to write | Example |
|---|---|---|
| URL | Full address of the page | https://lattuce.app/papers/… (your real path) |
| Steps | Numbered actions from a known start | 1. Open Library. 2. Upload a PDF. 3. Wait for ready. |
| Expected | What should have happened | The source shows ready and I can attach it |
| Actual | What happened instead | The row stays on “processing” after 20 minutes |
| Screenshot | Image of the error or wrong result | The banner, empty list, or failed export dialog |
| When | Date and rough time, plus browser | 19 June, Chrome on a laptop |
Optional extras that help when they are not secrets:
- File type (PDF, Word) and a rough size — not the file itself unless we ask
- Whether you were signed in, and whether a second household member sees the same thing
- Whether you tried the demo hub or a signed-in paper
What not to send
Do not paste anything that could open your account or your lab’s keys.
| Leave out | Why |
|---|---|
| Passwords, one-time codes, recovery phrases | We will never ask for these in a bug thread |
| API keys and provider tokens | Add keys only in your own account settings — never in Contact |
Session cookies or Authorization headers | Those are sign-in material |
| Full dumps of notes, emails, or student names | Describe the problem; redact names and emails in screenshots |
| Private PDF contents | Say “a 12-page scanned PDF” instead of attaching the thesis |
If a screenshot shows a key, cookie bar, or inbox, crop or blur it before you send.
How to send
- Open Contact.
- Say you are reporting a bug on lattuce.app during alpha.
- Paste the URL, numbered steps, expected vs actual, and attach the screenshot.
- Submit once. If the form fails, wait and try again — do not email keys to a side channel.
FAQ is the better first stop for billing and “how do I start” questions. Use Contact when something is broken.
After you send
Alpha means we ship often. We may ask one follow-up (browser, another screenshot, or “does it still happen?”). We will not ask you to paste secrets.
We warn before big changes to exports or saved work — see the alpha note in what alpha means. A bug report does not put your household on a public list.
If you decide Lattuce is not the right fit, Leaving Lattuce cleanly covers try-without-signup and account deletion.
Troubleshooting the report itself
| Symptom | What to do |
|---|---|
| You cannot copy a long URL | Write the path you see after lattuce.app and the button you clicked |
| The bug is “the site is slow” | Add which page, what you clicked, and roughly how long you waited |
| It happened once and you cannot repeat it | Send it anyway — say “could not reproduce,” plus the URL and time |
| Contact will not accept an image | Describe the screen in two sentences and note that a screenshot is available |
Related reading
- Lattuce at lattuce.app is in alpha — what works today and what may change
- Contact — questions, access issues, and bug reports
- Try Lattuce without signing up — sample workspaces before you import a library
- Leaving Lattuce cleanly — try first, delete if you need to
- FAQ — billing, privacy, getting started
Bottom line
On alpha, the most useful bug report is a URL, numbered steps, expected vs actual, and a screenshot — sent through Contact, with no secrets. That is enough for us to follow the same path on lattuce.app.
Bahasa Melayu: Maklum balas alfa — cara laporkan pepijat berguna di lattuce.app