Start with containment
If AutoQuill is typing into the wrong place or producing harmful input, stop the session before investigating. Close or minimize high-impact applications, save work, and move testing to a blank local editor.
Reproduce with the shortest possible text and a slow speed. Changing several options at once makes the cause harder to identify.
Wrong target or stolen focus
Symptoms include typing in another window, output appearing in a search field, focus moving after Tab or Enter, or typing stopping when a dialog opens.
- Stop AutoQuill.
- Bring the intended target forward.
- Click the exact field and confirm the caret.
- Reselect or verify the target.
- Remove Tab, Enter, modifier, and function-key commands.
- Run five plain characters.
- Watch for notifications and dialogs that steal focus.
Treat every focus transition as a new target-verification point.
Missed, duplicated, or transposed characters
| Symptom | Likely cause | First test |
|---|---|---|
| Missing characters | Speed too high or target lag | Reduce speed substantially |
| Repeated characters | Key-state/timing interaction | Fixed delays and plain text |
| Wrong case | Caps Lock, Shift, or input method | Reset lock state and test ASCII |
| Accented text corrupted | Layout or IME behavior | Short Unicode sample in the exact target |
| Order changes | Application event handling or load | Slow down and remove humanization |
Timing is inconsistent
Disable humanized timing and use a fixed slow rate. If that succeeds, add variation in small increments. System load, power saving, remote desktops, browser rendering, antivirus scans, and the target application can all affect timing. Measure actual completed output and total duration rather than requested WPM alone.
Commands trigger unexpected behavior
Commands are keys, not text. Tab can move focus, Enter can submit, Backspace/Delete can remove content, and modifiers/function keys can trigger shortcuts.
- Replace the sequence with plain text.
- Add one command.
- Test in a disposable target.
- Verify focus before and after.
- Check repetition counts.
- Document target shortcuts.
Application-specific behavior cannot be inferred from the profile alone.
Clipboard and dynamic tokens
The clipboard may contain stale, rich, sensitive, image, or file data. Copy intended plain text immediately before the run and inspect it manually. Date/time tokens depend on system clock, timezone, locale, and format; capture final expanded output when reproducibility matters.
Hotkey conflicts
Global hotkeys can conflict with Windows, accessibility tools, keyboard software, or the target application. Choose an unused combination, test with AutoQuill visible and hidden, close competing utilities, and retain a visible stop control.
Launch and profile-storage problems
Run AutoQuill from an extracted writable folder, not inside the ZIP or a protected system directory. Check whether security software quarantined files. If a profile fails after an update, create a fresh minimal profile before assuming all settings are incompatible.
Consult the AutoQuill changelog for current release context.
Build a minimal reproducible case
Ten ASCII characters in a blank editor.
No humanization, commands, or tokens.
Add only the failing command or token.
Determine whether the issue is application-specific.
Version, Windows build, settings, expected and actual output.
When to stop troubleshooting
Stop when the target can execute irreversible actions, automation is not authorized, or there is no reliable stop mechanism. Use paste, templates, an application-supported API, or manual entry instead.
Recovery after unintended typing
- Stop AutoQuill and disconnect the target from further automated action.
- Use the target application’s undo or version history when safe.
- Check whether Enter, shortcuts, or commands submitted data.
- Review logs, sent messages, commits, or changed records.
- Restore from a known version when necessary.
- Correct the profile and reproduce only in a disposable environment.
Do not assume that visible text is the only effect; keyboard shortcuts may have triggered hidden state changes.
Support report template
Include version, Windows build, keyboard layout/IME, target application and version, profile settings, exact minimal input, expected and actual output, reproduction rate, and whether it occurs in Notepad or another simple editor. Remove secrets and personal data before sharing screenshots or profiles.
Frequently asked questions
Focus or target state changed. Stop, focus the exact field, reverify the target, remove navigation commands, and test a few characters.
Reduce speed, disable humanization, close heavy applications, and test in a simple editor.
It uses the current clipboard. Inspect and recopy plain text immediately before the run.
AutoQuill version, Windows version, target, minimal profile, input, expected output, actual output, and whether it reproduces in a blank editor.
Sources and references
- AutoQuillJivaro · first-party
- AutoQuill ChangelogJivaro · first-party
- AutoQuill Setup GuideJivaro · first-party