尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Solve math questions from a screenshot
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Photograph a maths question from a textbook, worksheet, or screen. Pick a course, then choose Hint or Solve. Hint follows the tutor prompt for that course: one short hint or guiding question, and not the final answer. Solve gives the answer and the steps, using only ideas taught up through that course. The courses, in order, are Algebra 1, Algebra 2, Geometry, PreCalc, Calculus AB, Calculus BC, and Multivariable Calculus. Earlier courses get shorter steps and simpler words. If a problem needs a later course, the reply says so and stops at the selected course. Answers, steps, hints, and follow-ups render Markdown and LaTeX.
npm install
npm run dev
The dev server listens on http://127.0.0.1:43123 (0.0.0.0:43123).
Take a picture opens this device's camera in the page and captures a frame. Upload a photo picks an image you already have. Hint and Solve are the two run buttons. You can select one before the photo, and you press it again after the questions are listed. Crop the photo before anything else happens. Math Buddy then reads every question in the crop and waits. Choose all of the questions, or pick one from the list, then press Hint or Solve. The selected course is filled into the tutor prompt for a hint, and it sets the course ceiling for a solution.
Each finished hint or solve is saved in this browser with IndexedDB. The record keeps the course, the mode, the cropped picture, the questions that were found, which of them were used, the hint or the solution, the follow-up thread, and the model calls for that session. A model call is the question read, the hint or solve, or a follow-up: the course, the mode, the start and finish times, the text request, and the raw model reply. Those calls stay on the device. History opens a saved session on the page. The model calls for that session appear only in History, after the session is opened. A follow-up uses the same mode as that session.
The route POST /api/solve reads the first key it finds:
| Order | Environment variable | Model |
|---|---|---|
| 1 | OPENAI_API_KEY | gpt-4.1-mini |
| 2 | XAI_API_KEY | grok-4.6 |
| 3 | GROQ_API_KEY | qwen/qwen3.8-27b |
| 4 | ANTHROPIC_API_KEY | claude-sonnet-5 |
Copy .env.example to .env.local and set one key. Restart the dev server after you add it. If none of these variables is set, the page still loads and the solve button returns a clear message that a key is missing. Do not invent a key.