The challenge
Let people automate fragile browser tasks while keeping every step visible enough to understand, adjust, and trust.
All projectsIn development
Tools & automation
Automatic Task Helper
A desktop tool for turning repetitive browser work into reusable, understandable workflows.
- Role
- Product, UX & development
- Focus
- Browser automation
- Stage
- Active development
The project
Automatic Task Helper started with a very specific frustration: applying for jobs meant repeatedly navigating different application sites, entering the same information, and performing nearly identical browser actions. The first instinct was effectively to build a better job-application automator. Instead of tying the solution to one site or one application flow, the project evolved toward a more general question: could the repetitive browser actions themselves become reusable building blocks?
That shift turned the project into a Python desktop application for constructing browser-action queues. A user can define navigation, clicks, text input, delays, repeats, bulk operations, fallbacks, and conditional actions; preview which page elements a step will target; save the resulting workflow; and run it again later. What began as personal job-search automation became a general-purpose browser workflow tool that is functional for personal use while its remaining work is increasingly about hardening and productization rather than proving the core concept.
The approach
Treat browser work as a sequence of observable actions, then give an agent enough context to help build and recover those sequences without hiding what it is doing.
What matters
Built around the use case.
Reusable queues
Capture a routine once, then run the same sequence again when the work returns.
Human-readable steps
Clicks, entries, waits, and checks stay visible instead of disappearing into code.
Built for the messy web
Conditional steps help workflows handle pages that do not behave exactly the same every time.