FailPack

AI-ready failure reports from your CLI.

FailPack captures the exact failure context behind broken builds, command errors and regressions — then turns it into clean, redacted reports that are ready for AI assistants, GitHub issues, teammates and support.

• FailPack Dashboard

• FailPack API

FailPack is a local-first developer tool for packaging useful bug context without turning your project into a messy secret dump.

It helps you collect failed command output, logs, Git state, project metadata and sanitized environment context into structured reports that are easy to review, share and reuse.

Use it when you want to send a clean failure package to:

• an AI coding assistant,
• a teammate,
• a GitHub issue,
• a support channel,
• or your FailPack Cloud workspace.

Install the CLI globally:

npm install -g @failpack/cli

Then run FailPack inside the project you want to debug:

failpack

On first run, FailPack asks whether you trust the current folder and creates a local .failpackrc.json when accepted.

Capture a failing command:

failpack capture --cmd "npm run build"

Capture test output without creating a ZIP bundle:

failpack capture --cmd "npm test" --project ./my-app --no-zip

Generate AI-ready context from an existing error log:

failpack ai --error ./error.log --include-diff

Check the current report state:

failpack status

Mark a report version as fixed:

failpack fix v1

FailPack can collect and organize:

• failed command output,
• error logs,
• project metadata,
• Git branch and diff context,
• relevant runtime information,
• selected configuration signals,
• report status and version history,
• optional source context when explicitly enabled.

The goal is simple: give humans and AI enough context to understand the failure without manually pasting random terminal output, files and screenshots.

By default, FailPack writes local reports to:

.failpack/reports

A capture can produce:

A readable bug report for teammates, GitHub issues, support channels and internal debugging.

A prompt-shaped version of the failure context for AI assistants and coding agents.

Structured metadata for automation, dashboards and repeatable analysis.

An optional portable bundle for private sharing when a teammate or support channel needs the full package.

failpack
failpack capture --cmd "npm run build"
failpack capture --cmd "npm test" --project ./my-app --no-zip
failpack ai --error ./error.log --include-diff
failpack report --github --discord
failpack status
failpack fix v1
failpack unfix v2
failpack doctor
failpack init
failpack clean --yes

Cloud and AI commands:

failpack login
failpack whoami
failpack cloud upload
failpack cloud sync
failpack cloud open <id>
failpack cloud delete <id>
failpack analyze
failpack security

FailPack is designed to work locally first.

By default:

• reports are generated on your machine,
• cloud upload is always explicit,
• local commands work without login,
• generated Markdown can be reviewed before sharing,
• optional bundles are created only as part of the report flow.

Cloud features are available when you want report history, workspace visibility, AI analysis or team workflows.

FailPack is built to collect debugging context without exposing sensitive project data by accident.

Security-focused defaults include:

• common keys, tokens and credentials are redacted,
• .env files are ignored by default,
• private keys are ignored by default,
• cloud upload requires an explicit command or confirmation,
• AI and Cloud actions require a logged-in FailPack account.

You should still review generated reports before sharing them outside your machine or team.

FailPack Cloud adds workspace history, report versions, fixed/unfixed status tracking, team visibility and AI-assisted analysis.

Use Cloud when the debugging context needs to leave your machine safely:

failpack login
failpack cloud upload
failpack cloud sync
failpack analyze
failpack security

Local capture remains the default starting point.

FailPack service status is available at:

https://status.failpack.dev

Current monitored services:

• FailPack Dashboard

• FailPack API

• Website: https://failpack.dev
• Documentation: https://failpack.dev/docs
• Status page: https://status.failpack.dev
• NPM package: https://www.npmjs.com/package/@failpack/cli
• GitHub repository: https://github.com/Failpack/cli

FailPack is currently in early development.

The CLI, Cloud dashboard, AI analysis and security tooling are being improved continuously. Expect fast changes while the product moves toward a stable public release.