1
Sign In to Batman
Open the login page and click Sign In with your account credentials.
Download Link
Use these official links to sign in, buy credits, and download batman-01.exe.
2
Check Dashboard and Credits
After login, verify your account on the dashboard and check available credits. Click Buy Credits if needed.
3
Select Credits on Pricing Page
Go to the pricing page, choose how many credits you need, and click Pay Now.
4
Complete Payment
In the payment window, scan the QR code or choose a UPI method to complete payment successfully.
5
Download the EXE File
Open the Google Drive link and click Download anyway on the virus scan warning page.
6
Run batman-01.exe
Open the downloaded EXE. A command window should appear showing login success, credits, and registered hotkeys.
Sample Auto-Typing Video
Watch a quick Batman-0.1 runtime demo showing the auto-typing behavior.
Hotkeys Explained
Quick meaning of each registered shortcut from the app console output.
Ctrl + Print Screen
Takes a screenshot for assistant processing.
Ctrl + I
Sends confirm action to continue or submit the current assistant step.
F8
Pauses background assistant activity temporarily.
F9
Resumes activity after pause.
F10
Stops the running assistant workflow.
F2
Cycles processing speed mode.
F6
Opens or triggers login action.
F7
Shows account summary including available credits.
F12
Logs out from the current account session.
F4
Toggles assistant mode between available operation modes.
EXE Runtime Walkthrough
This walkthrough explains how batman-01.exe behaves from launch to auto-typing, using only the installed executable workflow.
1. App Startup and Login
Launch batman-01.exe, wait for the console to initialize, and complete login if prompted. Once signed in, your credits and active hotkeys are displayed in the running window.
2. Session and Account Flow
The app checks for an existing account session at startup. If no active session is found, it asks you to sign in before requests are allowed.
3. Screenshot Queue + Confirm Window
Press the screenshot hotkey one or more times. Captures are queued in order. Use the confirm hotkey inside the send window to submit immediately, or allow timeout behavior to continue flow.
4. Processing and Mode Routing
Submitted screenshots are processed in the currently active mode. If you switch between solve/debug modes, request behavior follows that mode until changed again.
5. Auto-Typing Output
After response generation, the app starts typing directly into your active text field. Typing speed and behavior follow the in-app controls available through hotkeys.
6. Pause, Resume, and Stop
During typing, use the pause key to hold output, resume to continue, and stop/reset when you need to clear the flow. These controls help handle interruptions without restarting the whole app.
7. Reliability and Fallback
If a screenshot send action is delayed or briefly fails, the app retries and keeps the queue stable. This improves consistency when typing is active or network conditions fluctuate.
8. Exit and Relaunch
Keep the EXE running while using hotkeys globally. Close the console window when done, then relaunch batman-01.exe whenever you want to start a new session.
Quick Usage Notes
This website supports users who run only batman-01.exe. You do not need source-code setup steps here. Focus on login, credits, screenshot queue flow, send confirmation timing, and hotkey controls.
For best stability, keep hotkeys unique, keep your target input focused before captures, and verify account credits before long sessions.
Complete User Tutorial Checklist
Use this as your full onboarding structure when explaining the app to new users.
1. What the App Is
- Background, no-GUI screenshot assistant controlled by hotkeys.
- Auto-types AI output into the active application window.
- Default workflow supports backend solve/debug routing.
2. System Requirements
- Windows environment with keyboard hooks and screen capture support.
- Downloaded batman-01.exe from the official link.
- Internet access for backend/API communication.
3. Accounts and Access
- Backend username/password required when backend mode is enabled.
- Login is prompted when no saved session/token exists.
- Session files are stored in local user app data scope.
4. Config to Explain
- All active hotkey mappings shown in the app console at startup.
- Confirmation send window timing and retry behavior.
- Backend URL, mode flags, and solve/debug endpoint options.
5. Full Hotkey Guide
- Screenshot, confirm send, pause, resume, stop/reset, speed cycle.
- Login, account summary, logout (with double-press confirm), mode toggle.
- Show users where hotkeys are printed during startup.
6. Real Usage Flow
- Start app, log in, focus target editor/input, capture screenshots.
- Confirm send in time window or let auto-send fallback trigger.
- Manage typing with pause/resume/stop and exit via Ctrl+C in terminal.
7. Solve vs Debug Mode
- Default mode is solve; users can toggle at runtime.
- Backend endpoint changes automatically based on current mode.
- Include endpoint verification for both solve and debug in docs.
8. Verification Steps
- Run batman-01.exe and confirm hotkeys are printed at launch.
- Sign in successfully and check account summary/credits.
- Capture screenshots, confirm send, and verify auto-typing begins.
- Test pause, resume, stop/reset, and mode toggle hotkeys once.
9. EXE Distribution
- Share only the official EXE download link from this tutorial page.
- Instruct users to keep the EXE in a trusted local folder.
- Document first-run login and basic hotkey verification for onboarding.
10. Troubleshooting
- Login failures, session expiry, and backend access restrictions.
- Send-confirm timeout and typing-in-progress delay cases.
- Hotkey conflicts and Windows build file lock issues.
11. Security Notes
- Never share token/session files or commit them to repositories.
- Keep session storage local-user scoped and private.
- Avoid showing credentials in recorded demos/screenshots.