No switching to a browser, no pasting screenshots into a chatbot, no losing your place. Guidelet reads whatever is on your screen, gives you the right amount of help, and draws a box around the exact control you need — on top of the app itself.
No plugins. No per-app setup. Nothing to integrate. Guidelet reads pixels, not APIs — so it works in anything you can see, including the app nobody has written a tutorial for.
Interactive product tour · seven apps · direct answers and guided walkthroughs
Four context switches to press one button.
You never looked away.

One shortcut, over whatever is in front — the bar names the app it is reading before you type a word. Word is still there, untouched, behind it.

Not a description of where the button is. A box on the button, numbered in the order you touch it.
Ask naturally. Guidelet works out whether the task needs one highlighted control or a route with several actions — you do not have to choose a mode first.
For a single action, Guidelet answers directly and marks the control to use.
For a longer task, it builds the actions on the fly and shows what the walkthrough will cover.
Start the route when you want guidance. Guidelet highlights the current action and checks the screen before moving on.
Word keeps its window and stays usable. The answer takes the side, the box stays on the button, and you carry on in the document you were already in.
Nothing here was built for a video editor. The same thing that finds a button in Word finds one in CapCut, Blender, or software with twelve users — because it looks at your screen the way you do.

Questions stay filed under the app you asked them in, so Word answers never mix with CapCut ones.
Keep an answer and its boxes for later. Reopen it the next time you need the same steps.
Drag a box around one panel and ask about that alone, instead of the whole screen.
It searches on its own when the app is niche, and lists the sources it used under the answer.
Send an answer with its highlighted screenshot to someone else, or save it to disk.
Ask the next question without leaving the app or losing the boxes already on screen.
Guidelet needs a view of the screen to answer a question, but that does not mean continuous recording. You decide when a capture happens.
No. Guidelet captures a still image only after you ask a question or approve a capture. It does not continuously record video or audio.
The captured still image, your question, the detected app name, relevant follow-up context, and an optional area you selected are sent to the answer service. If web search is on, the service may also send the question and relevant context to a search provider.
Your saved lessons, answer history, settings, and capture approvals are stored locally. Guidelet does not store captured screenshots in its account database by default.
Guidelet creates a stable one-way device code to prevent several accounts being used from the same Mac. The raw hardware identifier never leaves the Mac. The device-to-account binding remains until support deliberately releases it.
Guidelet uses service providers for answers, account access and usage limits, optional web results, website delivery, and waitlist email. Those providers may process or temporarily log information to operate and secure their services.
Delete local history and settings from the app. For account records, device release, waitlist removal, or another privacy request, email hello@guidelet.app.