lastexecrecord

Lightweight Windows console application. Every time it is invoked, it runs the commands registered in the JSON config once, in order, and skips commands when they should not run based on:

Last run time (seconds precision)
Minimum interval (seconds)

It avoids external libraries (Win32 API + STL only) and focuses on safe operation via config file locking and atomic updates.

Quick start

Run lastexecuterecord.exe (no arguments needed)
The app creates a sample config at %USERPROFILE%\.lastexecrecord\config.json
Edit the config file: set enabled: true and customize exe / args for your commands
Run lastexecuterecord.exe again to execute your commands

By default, the app reads %USERPROFILE%\.lastexecrecord\config.json. If this file doesn't exist, a minimal sample config is created automatically (with commands disabled by default for safety).

Installation

Using winget

winget install kkamegawa.lastexecrecord

After installation, you can run lastexecuterecord.exe from your terminal.

Usage

lastexecuterecord.exe: Run with default config (auto-creates sample if missing)
lastexecuterecord.exe --config : Specify a custom config JSON path
lastexecuterecord.exe --dry-run: Do not execute; only show decisions
lastexecuterecord.exe --verbose: Verbose logs (including skip reasons)

All options can be combined, for example: lastexecuterecord.exe --config myconfig.json --dry-run --verbose

Windows Terminal Profile Setup

To register lastexecuterecord.exe as a Windows Terminal profile and continue running PowerShell or Command Prompt after execution, add the following profile to your Windows Terminal settings.json:

{
  "profiles": {
    "list": [
      {
        "name": "lastexecrecord + PowerShell",
        "commandline": "cmd.exe /c lastexecuterecord.exe &amp;&amp; pwsh.exe",
        "icon": "ms-appx:///ProfileIcons/PowerShell.png"
      },
      {
        "name": "lastexecrecord + Command Prompt",
        "commandline": "cmd.exe /c lastexecuterecord.exe &amp;&amp; cmd.exe",
        "icon": "ms-appx:///ProfileIcons/CommandPrompt.png"
      }
    ]
  }
}

&& executes the next shell only if lastexecuterecord.exe exits successfully
Use ; instead of && if you want to continue regardless of exit code: cmd.exe /c lastexecuterecord.exe ; pwsh.exe

To edit settings.json, open Windows Terminal and press Ctrl + , or click the Settings icon.

Config schema (version 1)

Example: lastexecuterecord.sample.json

Root fields

version (number, optional): Default is 1
networkOption (number, optional): Control execution based on network status. Default is 2
- 0: Execute only when internet is connected (not on metered connections)
- 1: Execute even on metered connections (internet connection required)
- 2: Always execute (ignore network status)
defaults.minIntervalSeconds (number, optional): Default minimum interval for commands
defaults.timeoutSeconds (number, optional): Default timeout for commands
defaults.installerWaitBehavior (string or number, optional): Default behavior when installer is running. Default is "wait"
- "wait" or 0: Wait for installer to finish before executing
- "skip" or 1: Skip command if installer is running
defaults.installerWaitSeconds (number, optional): Wait time in seconds between installer checks. Default is 30
defaults.installerMaxRetries (number, optional): Maximum number of retries when waiting. Default is 10
commands (array, required): List of commands to run (processed from top to bottom)

Command fields

name (string, required): Display name / identifier
enabled (bool, optional): Default is true
exe (string, required): Executable path (not a shell string; use exe + args)
args (array of string, optional): Arguments
workingDirectory (string, optional)
minIntervalSeconds (number, optional): Defaults to defaults.minIntervalSeconds
timeoutSeconds (number, optional): Defaults to defaults.timeoutSeconds
installerWaitBehavior (string or number, optional): Behavior when installer is running. Defaults to defaults.installerWaitBehavior
installerWaitSeconds (number, optional): Wait time between checks. Defaults to defaults.installerWaitSeconds
installerMaxRetries (number, optional): Maximum retries. Defaults to defaults.installerMaxRetries
lastRunUtc (string, optional): Example 2026-01-02T12:34:56Z (seconds precision)
lastExitCode (number, optional): Previous exit code

sample(winget)

{
  "version": 1,
  "defaults": {
    "minIntervalSeconds": 64800,
    "timeoutSeconds": 0
  },
  "commands": [
    {
      "name": "winget",
      "enabled": true,
      "exe": "c:\\windows\\system32\\sudo.exe",
      "args": [
        "winget",
        "upgrade",
        "--all",
        "--accept-package-agreements",
        "--silent"
      ]
    }
  ]
}

Notes (security)

The config uses exe + args[] and does not assume shell execution like cmd.exe /c (helps reduce injection risk).
To prevent concurrent runs, the program acquires an exclusive .lock file.
DO NOT use environment variables or user input to construct exe or args in the config file, as this may lead to command injection vulnerabilities.

Installer detection and wait behavior

If a Windows installer process (such as msiexec.exe) is running in the background, some installers launched by this program may fail. To handle this scenario, the application can:

Wait for the installer to finish before executing commands (default behavior)
Skip execution if an installer is detected

This behavior is controlled by the installerWaitBehavior configuration field (either globally in defaults or per-command).

How it works

Before executing each command, the application checks if any of the following installer processes are running:
- msiexec.exe (Windows Installer)
- setup.exe, install.exe, setupapi.exe, msiinstall.exe, windows installer.exe
If an installer is detected and installerWaitBehavior is "wait" (default):
- The application waits for installerWaitSeconds seconds (default: 30 seconds)
- Then checks again if the installer is still running
- This repeats up to installerMaxRetries times (default: 10 retries)
- If the installer finishes, the command is executed
- If the installer is still running after all retries, the command is skipped
If an installer is detected and installerWaitBehavior is "skip":
- The command is immediately skipped

Example configuration

{
  "defaults": {
    "installerWaitBehavior": "wait",
    "installerWaitSeconds": 30,
    "installerMaxRetries": 10
  },
  "commands": [
    {
      "name": "system update",
      "exe": "winget.exe",
      "args": ["upgrade", "--all"],
      "installerWaitBehavior": "wait"
    }
  ]
}

Development

Building

This project uses Visual Studio 2022/2025 or MSBuild.

Visual Studio:

Open src\lastexecrecord.sln in Visual Studio
Build -&gt; Build Solution

MSBuild (command line):

msbuild src\lastexecrecord.sln /p:Configuration=Release /p:Platform=x64

For other platforms:

REM Debug build for x64
msbuild src\lastexecrecord.sln /p:Configuration=Debug /p:Platform=x64

REM Release build for ARM64
msbuild src\lastexecrecord.sln /p:Configuration=Release /p:Platform=ARM64

Testing

Tests have been migrated to Microsoft Unit Testing Framework for C++ (MSTest).

Run tests in Visual Studio:

Open src\lastexecrecord.sln in Visual Studio
Build the solution (Ctrl+Shift+B)
Open Test Explorer (Test → Test Explorer)
Click "Run All" to execute all tests

See src/lastexecuterecord.mstest/ for the test project and src/docs/MSTEST-MIGRATION.md for migration details.

lastexecrecord Kazushi Kamegawa

README