Click the Help button on any page and Aidelly’s Page Tutor knows exactly where you are and what the page does. Ask a question, get a contextual answer in seconds. Read-only by design — the tutor never touches your data.
The tutor knows what page you’re on, what it does, and what tasks belong there.
No tools, no mutations. The tutor can’t accidentally publish, delete, or change a thing.
Runs on the latest Haiku model — answers stream in seconds, not minutes.
Each page suggests the top 3–5 questions other users actually ask there.
Ask in any of Aidelly’s 8 interface languages — the tutor responds in your language.
History lives in sessionStorage on your device. Never stored server-side, never used for training.
Daily message cap per workspace + lightweight Haiku model = predictable AI spend.
Tutor explains. Chat does. Both ship in the same Help button.
Bottom-right corner of any page. Opens to the Tips tab; switch to "Tutor".
"What does this toggle do?" / "How do I add a destination here?" / "What’s the difference between X and Y?"
Page-aware, brand-aware, and source-cited where relevant. No tool calls, no mutations.
Conversation stays in the panel as you navigate. Switch pages and the tutor swaps context with you.
A small AI chat panel inside Aidelly’s Help button. It already knows which page you’re on and what the page does, so you can ask "how do I set this up?" or "what does this toggle do?" without leaving your workflow. Answers stream back in seconds.
Chat is the full agent — it has tools, can mutate state, can publish posts, and is built to do work on your behalf. The tutor is read-only: no tools, no mutations, no calls to other Aidelly endpoints. Its only job is to explain the page you’re looking at.
Most of the app. Each page registers its own tutor context — the page name, what it does, common tasks, and suggested questions. New pages added to Aidelly inherit the same pattern, so the tutor coverage stays current.
No. By design, the tutor is read-only. If you want it to do a thing — schedule a post, edit a draft, run an automation — switch to /chat where the full agent has tool access. Splitting "explain" from "do" keeps the tutor safe to use exploratorily.
Yes, but lightly. The tutor runs on Haiku with short context — typically 2–8 credits per question. Each workspace has a daily message cap to keep cost bounded; you’ll see the remaining count in the panel.
The conversation lives in sessionStorage, scoped to your workspace + page, and is kept locally on your device for the session. It is not stored on Aidelly servers and not used to train models. Closing the tab clears the local cache.