Skip to main content

Bad Decisions terminal client

bad-decisions-client is a dependency-free terminal client for a Bad Decisions service. It contains no card corpus and runs on Linux, macOS, and Windows.

Install

On macOS and Linux, Homebrew is the suggested install. It also sets up man regret with no shell changes:

brew install bytesandcoffee/tap/regret

Otherwise use pipx, which keeps regret in its own environment and also links its manual page, or plain pip:

pipx install bad-decisions-client
python -m pip install bad-decisions-client

regret doctor checks an install and prints the fix for anything wrong, without changing anything. For example, with pyenv or another version manager that puts shims on PATH, man regret cannot find the page pip installed, and doctor prints the MANPATH line to add to your shell profile.

Use

regret health
regret deal
regret deal --packs base,maha
regret provenance
regret provenance --json
regret --list-packs
regret doctor

Join an ephemeral multiplayer room with Peer Pressure:

regret together ohno --name Michael

The first participant is the initial Responsible Adult. Regret securely caches the room-local reconnect capability, maintains heartbeats while connected, and automatically resynchronizes stale state. Peer Pressure identity is separate from Consequences analytics identity. See the multiplayer documentation.

Consequences is opt-in and disabled until you choose:

regret consequences status
regret consequences enjoy
regret consequences regret

The first interactive deal prompts once when no preference is stored; non-interactive runs remain disabled. When enabled, voting and its pseudonymous telemetry are available. The client also performs a cached, best-effort daily check against the configured API version.

regret provenance prints the licenses, attribution, versions, and source records for every pack represented in the last locally saved draw. It does not make a network request. A successful draw with provenance replaces the saved record; feedback capability details are retained only when that same draw is eligible for voting.

The default endpoint is https://bytes.coffee/bad-decisions. Use --api-url for another compatible deployment. Connection and API failures return a non-zero exit status.

Changelog

See CHANGELOG.md for client release notes.

Release

Build and validate before uploading a new immutable PyPI version:

cd client
python -m build
twine check dist/*

Metadata

Release files for bad-decisions-client 2.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bad-decisions-client 2.0.1
File Size Uploaded
bad_decisions_client-2.0.1.tar.gz 21.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for bad-decisions-client 2.0.1
File Interpreter ABI Platform
bad_decisions_client-2.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 38.9 kB

Release files / bad_decisions_client-2.0.1.tar.gz

Download URL bad_decisions_client-2.0.1.tar.gz
Size 21.8 kB
Tags Source
SHA-256 checksum
How to use checksums
046d65ec2b78cbc646b9cd4a133ec4b30636f87b43057c9908e1086786214ba0
BLAKE2b-256 checksum
How to use checksums
75c078f0cecc2e14b5424692d9937754187920edbd3d173177b538503414d25c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.

Transparency log

Release files / bad_decisions_client-2.0.1-py3-none-any.whl

Download URL bad_decisions_client-2.0.1-py3-none-any.whl
Size 17.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7a3146f23b21a594e06fa97e1aed5c0aa15f7f72226d874347f84317b436fdf5
BLAKE2b-256 checksum
How to use checksums
99e09ed2707068bffc26eb16bd3c38b06f6fcafda1b090de68a866ac7278faef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.

Transparency log

Release history Release notifications | RSS feed

2.3.0

2 release files

2.2.2

2 release files

2.2.1

2 release files

2.2.0

2 release files

2.1.6

2 release files

2.1.5

2 release files

2.1.4

2 release files

2.1.3

2 release files

2.1.2

2 release files

2.1.1

2 release files

2.1.0

2 release files

2.0.3

2 release files

2.0.2

2 release files

This release

2.0.1 This release

2 release files

2.0.0

2 release files

1.8.5

2 release files

1.8.4

2 release files

1.8.3

2 release files

1.8.2

2 release files

1.8.1

2 release files

1.6.3

2 release files

1.6.2

2 release files

1.6.1

2 release files

1.6.0

2 release files

1.5.0

2 release files

1.4.1

2 release files

1.2.2

2 release files

1.2.1

2 release files

1.2.0

2 release files

1.1.9

2 release files

1.1.8

2 release files

1.1.4

2 release files

1.1.3

2 release files

1.1.2

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page