The stack history command lists recent recorded Stacktape operations with their status. Each entry shows success or failure status, timestamps, and error descriptions for failed operations. Use filters to narrow results by project, stage, or the current API-key user.
Usage
stack history returns the 25 most recent operations across all projects and stages in your organization. You must be logged in with a valid API key — run stacktape login first if you haven't already.
Filtering results
Filter by project name to see operations for a single project.
Filter by stage to see operations for a specific stage across all projects.
Combine --project and --stage to narrow results to a single project and stage.
Show only operations triggered by your own API key.
Controlling output size
By default, stack history returns the 25 most recent operations. Use --limit to change this.
Machine-readable output
Use --agent or --json to get machine-readable output suitable for scripts or AI coding agents. See the flags reference below for details on each output format.
Flags reference
stacktape stack historyCLI options--current-user-onlybooleanCurrent User Only
If true, only returns records created by the user that owns the active API key.
-h, --helpstringShow Help
If provided, the command will not execute and will instead print help information.
--limitnumberLimit
Maximum number of items to return.
--log-level"info" | "debug" | "error"Log Level
The level of logs to print to the console.
info: Basic information about the operation.error: Only errors.debug: Detailed information for debugging.
--projectstringProject Name
The name of the Stacktape project for this operation.
Commands that target a stack take it from projectName in the project's config when the flag is absent.
--quietbooleanQuiet
Hide progress, banners, success messages and hints. Command output, warnings and errors are still printed.
-s, --stagestringStage
The stage for the operation (e.g., production, staging, dev-john). You can set a default stage using the defaults set command. Stage names use lowercase letters, numbers and dashes, with at least 2 characters. The project name, a dash and the stage form the CloudFormation stack name, which can have at most 128 characters. Stacktape shortens an AWS resource name that would be too long and adds a hash.
Related commands
stack list— list all deployed stacks in a region with their status and estimated spend.status— show detailed outputs and resources for a specific deployed stack.whoami— verify your API key and see which organization, AWS accounts, and projects you have access to.