Ghostbit CLI
Command-line tool for Ghostbit — a self-hosted, end-to-end encrypted paste service.
All content is encrypted in the client before being sent to the server. The server never sees your plaintext.
Install
pip install ghostbit-cli
With syntax highlighting and Markdown rendering:
pip install "ghostbit-cli[all]" # pygments + rich
pip install "ghostbit-cli[color]" # pygments only (syntax highlighting)
pip install "ghostbit-cli[markdown]" # rich only (Markdown rendering)
Usage
# Paste from stdin
cat file.py | gbit
# Paste a file (language auto-detected from extension)
gbit file.py
# With options
gbit file.py --lang python --burn --expires 3600
# Password-protected paste (prompted securely)
echo "secret" | gbit -p
# Or pass inline (visible in process list)
gbit file.py --password mysecret
# View and decrypt a paste in the terminal
gbit view https://paste.example.com/abc123#KEY~TOKEN
# View a password-protected paste (prompts for password)
gbit view https://paste.example.com/abc123#~TOKEN
# Output JSON (includes full URL with decryption key)
cat data.json | gbit --json
# Point to your self-hosted instance
gbit config set server https://paste.example.com
Options
| Flag | Short | Description |
|---|---|---|
--lang |
-l |
Language hint (python, go, rust, …) |
--expires |
-e |
TTL in seconds (3600 = 1h, 86400 = 1d) |
--burn |
-b |
Delete after the first view |
--max-views |
-m |
Delete after N views |
--password |
-p |
Encrypt with a password (prompted if no value given) |
--server |
-s |
Override server URL for this call |
--quiet |
-q |
Print URL only |
--json |
Print full JSON response | |
--no-history |
Don't save to local history | |
--version |
-V |
Print version and exit |
Configuration
gbit config set server https://paste.example.com
gbit config show
gbit config unset server
Config is stored at ~/.config/ghostbit.toml.
Security Note
The local history (~/.local/share/ghostbit/history.jsonl) stores full URLs including decryption keys. Use --no-history for sensitive pastes, or clear history with gbit list --clear.
Self-hosting
See the Ghostbit server repository for Docker and manual setup instructions.
License
MIT
Release files for ghostbit-cli 1.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ghostbit_cli-1.5.0.tar.gz | 14.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ghostbit_cli-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.3 kB
Release files / ghostbit_cli-1.5.0.tar.gz
| Download URL | ghostbit_cli-1.5.0.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f8f8b464fa3fd2f4443dbb73ab06f6cde3653646a72cc2872a161febf2e7a1c
|
|
BLAKE2b-256 checksum How to use checksums |
a67140bdbbd9774df5b18b14d640390acca28d7ff3b5644362bb52fd2df7619b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 24, 2026.
Transparency logRelease files / ghostbit_cli-1.5.0-py3-none-any.whl
| Download URL | ghostbit_cli-1.5.0-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d55474a83b8ea713f9d2cdfe9fdc77de0284db0627196542890154bc1c83adcb
|
|
BLAKE2b-256 checksum How to use checksums |
74c41ccba6adb279fd85985f16c91309f5b30cc449d0b76c87d2e840e95b2851
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 24, 2026.
Transparency log