TinyTask Command Line: Run Macros from CMD, Batch Files, and Scripts

1. Does TinyTask Have a Command Line Interface?

TinyTask does not have a built-in CLI with flags and arguments. You cannot pass parameters like tinytask.exe --play macro.rec --loop 5 --speed 2x the way you might with AutoHotkey or other scripting tools. TinyTask is a GUI application designed for point-and-click simplicity.

However, TinyTask has a feature that makes command line usage possible: compiling macros to standalone .exe files. A compiled macro is a self-contained executable that runs the recorded sequence when launched. Since it is an .exe, you can call it from the command prompt, batch files, PowerShell scripts, and Windows Task Scheduler.

2. Step 1: Compile Your Macro to EXE

Before you can run a TinyTask macro from the command line, you need to compile it into an executable file. This is a required step — .rec files cannot be run from CMD directly.

3. Running Compiled Macros from CMD

Once compiled, your macro is just an .exe file. Open Command Prompt and run it like any other program.

Basic execution

C:\Macros\my-macro.exe

This launches the macro and returns control to the command prompt after the process starts. The macro runs in the background.

Using START for non-blocking execution

start "" "C:\Macros\my-macro.exe"

The start command launches the .exe in a separate process. The command prompt does not wait for the macro to finish before accepting the next command. Useful in batch files where you want to continue processing while the macro runs.

Using START /WAIT for blocking execution

start /wait "" "C:\Macros\my-macro.exe"

The /wait flag tells the command prompt to wait until the macro finishes before continuing. This is important in batch files where the next command depends on the macro completing first.

Running from a different directory

cd C:\Macros
my-macro.exe

Or use the full path without changing directories. Always use quotes around paths with spaces:

"C:\Users\John Smith\Macros\daily report.exe"

4. Creating Batch Files for TinyTask Macros

Batch files (.bat) let you automate the launch of your compiled macros with additional logic like delays, conditions, and sequencing.

Basic batch file

Create a text file called run-macro.bat with:

@echo off
echo Starting macro...
start /wait "" "C:\Macros\my-macro.exe"
echo Macro finished.
pause

Double-click the .bat file to run the macro. The window shows status messages and waits for you to press a key before closing.

Batch file with delay

@echo off
echo Waiting 10 seconds before starting...
timeout /t 10 /nobreak >nul
echo Starting macro now.
start /wait "" "C:\Macros\my-macro.exe"
echo Done.

The timeout command pauses for a specified number of seconds. Use this when you need time to position a window or load an application before the macro starts clicking.

Batch file with loop

@echo off
echo Running macro 5 times...
for /L %%i in (1,1,5) do (
    echo Run %%i of 5
    start /wait "" "C:\Macros\my-macro.exe"
    timeout /t 3 /nobreak >nul
)
echo All runs complete.

This runs the macro 5 times with a 3-second pause between each run. Adjust the numbers in (1,1,5) — the third number is the total count. The timeout between runs gives applications time to reset to a clean state.

5. Chaining Multiple Macros

Sometimes a workflow requires multiple macros to run in sequence. Compile each step as a separate .exe, then chain them in a batch file.

@echo off
echo Step 1: Opening application...
start /wait "" "C:\Macros\step1-open-app.exe"
timeout /t 5 /nobreak >nul

echo Step 2: Filling the form...
start /wait "" "C:\Macros\step2-fill-form.exe"
timeout /t 2 /nobreak >nul

echo Step 3: Submitting and saving...
start /wait "" "C:\Macros\step3-submit.exe"
timeout /t 2 /nobreak >nul

echo Step 4: Closing application...
start /wait "" "C:\Macros\step4-close.exe"

echo Workflow complete.

Why chain macros instead of one long recording?

• Modularity: Fix or re-record one step without redoing the entire workflow.
• Timing control: Add custom delays between steps using timeout.
• Conditional logic: Use if exist or if errorlevel to skip steps based on conditions.
• Reusability: Use step1-open-app.exe in multiple workflows.

Conditional execution

@echo off
if exist "C:\Reports\daily.xlsx" (
    echo Report exists. Running update macro...
    start /wait "" "C:\Macros\update-report.exe"
) else (
    echo Report not found. Running create macro...
    start /wait "" "C:\Macros\create-report.exe"
)

This checks if a file exists before deciding which macro to run. Useful when the workflow depends on whether a previous step has already completed.

6. Scheduling Macros with Task Scheduler

Windows Task Scheduler can run your compiled macros at specific times without any human interaction. This is the closest TinyTask gets to true unattended automation.

7. Running Macros from PowerShell

PowerShell offers more control than CMD for launching and managing macro processes.

Basic execution

# Run macro and wait for completion
Start-Process -FilePath "C:\Macros\my-macro.exe" -Wait

# Run macro without waiting
Start-Process -FilePath "C:\Macros\my-macro.exe"

Run with timeout (kill if it takes too long)

# Start the macro
$proc = Start-Process -FilePath "C:\Macros\my-macro.exe" -PassThru

# Wait up to 60 seconds
$finished = $proc.WaitForExit(60000)

# Kill if still running
if (-not $finished) {
    $proc | Stop-Process -Force
    Write-Host "Macro timed out and was terminated."
} else {
    Write-Host "Macro completed successfully."
}

This is useful for continuous-loop macros that need to run for a set duration and then stop. The timeout is in milliseconds (60000 = 60 seconds).

Run macro and log output

$timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
$logFile = "C:\Macros\log.txt"

Add-Content $logFile "$timestamp - Starting macro"
$proc = Start-Process -FilePath "C:\Macros\my-macro.exe" -PassThru -Wait
Add-Content $logFile "$timestamp - Macro finished (Exit code: $($proc.ExitCode))"

Loop with custom intervals

for ($i = 1; $i -le 10; $i++) {
    Write-Host "Run $i of 10"
    Start-Process -FilePath "C:\Macros\my-macro.exe" -Wait
    Start-Sleep -Seconds 5
}
Write-Host "All runs complete."

8. Real-World Command Line Workflows

9. Troubleshooting Command Line Execution

Macro runs but clicks in wrong positions

Screen resolution or DPI scaling changed since the macro was recorded. Compiled macros use absolute pixel coordinates. If you moved to a different monitor or changed display settings, re-record and recompile the macro at the current resolution.

Batch file closes immediately without running

The path to the .exe is wrong or has unescaped spaces. Always wrap paths in double quotes: "C:\My Macros\daily report.exe". Add pause at the end of the batch file to see error messages before the window closes.

Task Scheduler runs the macro but nothing happens

The task is running in a background session where no desktop is visible. TinyTask macros need an active, unlocked desktop. Make sure the user is logged in, not locked, and the task is configured to “Run only when user is logged on” (not “Run whether user is logged on or not”).

Macro starts but the target application is not ready

Add a timeout /t 10 delay in the batch file before starting the macro. If launching an application first, use start /wait to let it fully load before the macro begins clicking.

Compiled EXE is flagged by antivirus

TinyTask compiled .exe files simulate keyboard and mouse input, which some antivirus programs flag as potentially unwanted. Add an exception for the .exe file or the folder containing your macros in your antivirus settings.

Cannot stop a looping macro launched from CMD

Press Ctrl+Shift+Alt+P (TinyTask’s stop hotkey) or open Task Manager (Ctrl+Shift+Esc), find the macro process, and click “End Task.” For PowerShell, use the timeout-and-kill pattern shown in section 7.

10. Frequently Asked Questions