Skip to main content

Core Agent Loop API

FastAPI application providing Server-Sent Events (SSE) endpoint for Claude SDK agent interactions.

Project Structure

core_agent_loop/
├── app/
│   ├── __init__.py
│   ├── main.py                 # FastAPI application entry point
│   └── router/
│       ├── __init__.py
│       └── agent.py            # Agent loop SSE endpoint
├── config.py                   # Configuration settings
├── add_keyword_test.py         # Original test script
├── requirements.txt            # Python dependencies
└── env.local                   # Configuration file (rename to .env)

Setup

  1. Install dependencies:

    pip install -r requirements.txt
    
  2. Configure environment:

    cp env.local .env
    # Edit .env to add your Langfuse credentials if needed
    
  3. Ensure Claude CLI is installed and configured:

    claude --version
    

Running the Server

# Start all services (FastAPI on 8334, Claude-Mem Manager on 37777, File API on 38888)
docker-compose up -d

# View logs
docker-compose logs -f

# Stop services
docker-compose down

The FastAPI server will be available at http://localhost:8334
The Claude-Mem Manager UI will be available at http://localhost:37777/switch_user
All other traffic on port 37777 will be proxied to the active claude-mem worker
The File API service will be available at http://localhost:38888 The CLI wheel server will be available at http://localhost:11113

Using Python directly:

python -m app.main

Using Uvicorn:

uvicorn app.main:app --reload --host 0.0.0.0 --port 8334

The server will start at http://localhost:8334

CLI Auto Upgrade

Install from PyPI:

python -m pip install --upgrade pip
python -m pip install --upgrade luckee-cli

PyPI releases are wheel-only (no source distribution) and are published for:

  • Linux x86_64
  • Linux aarch64
  • macOS x86_64
  • macOS arm64
  • Windows x86_64

If your platform/architecture is outside this matrix, pip will not find a compatible wheel.

If you want to validate a dev publish first, install from TestPyPI:

python -m pip install --upgrade \
  --index-url https://test.pypi.org/simple/ \
  --extra-index-url https://pypi.org/simple \
  luckee-cli

For the staging CLI, set the environment before login/use:

export LUCKEE_ENV=staging

This selects both the staging OAuth API (staging-user-api.motse.ai) and the staging frontend automatically. LUCKEE_OAUTH_BASE_URL / LUCKEE_FRONTEND can still override individual URLs when needed.

CLI auth helpers:

luckee login
luckee logout

Published defaults:

  • LUCKEE_ENV=staging → OAuth API staging-user-api.motse.ai, frontend luckee-frontend-staging-…
  • LUCKEE_ENV=prod (default) → OAuth API user-api.motse.ai, frontend motse.ai
  • dev branch builds default WebSocket endpoint to wss://core-agent-loop-dev-950663559455.us-central1.run.app/api/v2/agent/ws
  • main branch builds default WebSocket endpoint to wss://core-agent-loop-950663559455.us-central1.run.app/api/v2/agent/ws
  • dev branch builds default File API base URL to https://file-api-dev-950663559455.us-central1.run.app
  • main branch builds default File API base URL to https://file-api-main-950663559455.us-central1.run.app

Upgrade the installed CLI:

luckee --upgrade

Or while inside interactive CLI:

/upgrade

CLI Development

For local luckee CLI development and packaging validation, use the dedicated guide:

Shortest repeatable local validation loop:

conda activate core_agent_loop
python scripts/validate_cli_dev_loop.py

That helper repairs stale editable CLI metadata, validates both local entrypoints, and builds a fresh wheel. Use python scripts/validate_cli_dev_loop.py --with-pipx --remote-smoke ... when you also want packaged remote validation.

API Endpoints

Root

  • GET / - API information and available endpoints

Health Check

  • GET /health - Health check endpoint

Agent Test

  • GET /api/agent/test - Test the agent router

Agent Stream (SSE)

  • POST /api/agent/stream - Stream agent responses via Server-Sent Events

Request Body:

{
  "query": "add a keyword test_keyword_1",
  "thread_id": null,
  "user_id": "dylan",
  "working_dir": null,
  "system_prompt": null
}

Response: Server-Sent Events stream with structured state messages.

File API (Port 38888)

  • GET /api/v2/resume_thread - Resume a thread by streaming messages (SSE)
  • GET /api/v2/list_threads - List all thread IDs for a user
  • GET /api/v2/fetch_files - Fetch files from user directories

Resume Thread (SSE) Query Parameters:

  • thread_id: Thread ID (must be a valid UUID)
  • user_id: User ID

Resume Thread Example:

curl -N "http://localhost:38888/api/v2/resume_thread?thread_id=550e8400-e29b-41d4-a716-446655440000&user_id=dylan"

The stream always starts with a config message containing metadata from working_dir/metadata.json, followed by all messages from streaming_messages.jsonl, and ends with a completion event.

List Threads Query Parameters:

  • user_id: User ID

List Threads Example:

curl "http://localhost:38888/api/v2/list_threads?user_id=dylan"

Fetch Files Query Parameters:

  • type: Type of file to fetch (csv, json, or json_folder)
  • thread_id: Thread ID (must be a valid UUID string)
  • path: Relative path to the file from working_dir
  • user_id: User ID

Examples:

Fetch a JSON file:

curl "http://localhost:38888/api/v2/fetch_files?type=json&thread_id=550e8400-e29b-41d4-a716-446655440000&path=data/config.json&user_id=dylan"

Fetch a CSV file:

curl "http://localhost:38888/api/v2/fetch_files?type=csv&thread_id=550e8400-e29b-41d4-a716-446655440000&path=data/report.csv&user_id=dylan"

Fetch all JSON files from a folder:

curl "http://localhost:38888/api/v2/fetch_files?type=json_folder&thread_id=550e8400-e29b-41d4-a716-446655440000&path=data/json_files&user_id=dylan"

Response Format:

  • For csv/json: Returns content of the file
  • For json_folder: Returns a dict mapping filename to content for all *.json files

Security:

  • Path traversal protection is enforced
  • Files must exist under /data/{user_id}/projects/{thread_id}/working_dir/{path}

Session Management

The agent supports session resumption based on thread_id. The project state (including the Claude SDK session ID) is stored in /data/${user_id}/projects/${thread_id}/working_dir/metadata.json.

To resume a session, include the thread_id in subsequent requests:

{
  "query": "continue with the next task",
  "thread_id": "previous_thread_id",
  "user_id": "dylan"
}

If a thread_id is provided but no existing session is found in the project metadata, the API will return an error.

Development

Architecture Documentation

For detailed information about the system architecture, modules, and design patterns, see:

Original Test Script

The original CLI test script is still available:

python add_keyword_test.py --query "add a keyword test_keyword_1"

License

MIT

Metadata

Release files for luckee-cli 0.1.20261102052119548

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

Built distributions (wheels)

Table of built distributions (wheels) for luckee-cli 0.1.20261102052119548
File Actions
luckee_cli-0.1.20261102052119548-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for luckee_cli-0.1.20261102052119548-cp312-cp312-win_amd64.whl
luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_11_0_arm64.whl
luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details for luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_10_13_x86_64.whl
luckee_cli-0.1.20261102052119548-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for luckee_cli-0.1.20261102052119548-cp311-cp311-win_amd64.whl
luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_11_0_arm64.whl
luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details for luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_10_9_x86_64.whl
luckee_cli-0.1.20261102052119548-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for luckee_cli-0.1.20261102052119548-cp310-cp310-win_amd64.whl
luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_11_0_arm64.whl
luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_10_9_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.9+ x86-64 Details for luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_10_9_x86_64.whl

Total release size: 50.3 MB

Release files / luckee_cli-0.1.20261102052119548-cp312-cp312-win_amd64.whl

Download URL luckee_cli-0.1.20261102052119548-cp312-cp312-win_amd64.whl
Size 819.9 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
c555f911663220c7459ba6c2c48e31207346511ddf3e7d488cf49ed315ab8dff
BLAKE2b-256 checksum
How to use checksums
edb39f545b882ab65e9b3e3e2b187df623b56e6cf35588b51817b773e88f845b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 7.1 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
45ff52bdbf6547d61edb267446872eb9b69f01ca08ba2005e4e5eedea21c6417
BLAKE2b-256 checksum
How to use checksums
f6129b9b64c32261ef0455e38aead15062671fa91d65cb1131be91296bed187c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL luckee_cli-0.1.20261102052119548-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 6.8 MB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
6409917bbcb78d1735fc0c0e774ba7d19c669e15da4f89fb79a0b9ece2b4367f
BLAKE2b-256 checksum
How to use checksums
2815ba4791d722e3b8972379242cfaeecfed384bc91113031a9e7ef6e11606d7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_11_0_arm64.whl

Download URL luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_11_0_arm64.whl
Size 868.4 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
7225ff08caa7634765e41426fab7708ad07a55a88146c92fe12677389bda3310
BLAKE2b-256 checksum
How to use checksums
de968854b9ec64b6e37c8aa68d3a851c888c608bf1fa24aa3ad3de9a700635ac
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_10_13_x86_64.whl

Download URL luckee_cli-0.1.20261102052119548-cp312-cp312-macosx_10_13_x86_64.whl
Size 971.0 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
aa1c3a5bebe1bfadf2a23912f4d8a12599e765e4a5097df790289a7de8ce5c4d
BLAKE2b-256 checksum
How to use checksums
36e33107b8f218038e68cef2f6638071b5ecffa6ef0ebf6030001ea596d90aa9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp311-cp311-win_amd64.whl

Download URL luckee_cli-0.1.20261102052119548-cp311-cp311-win_amd64.whl
Size 849.0 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
e0d3327b2d66caaae21e11516ba8bf5824f9dd07cfd01e179ee97cd6dba00726
BLAKE2b-256 checksum
How to use checksums
185aa47dba3f8e580f2f5d91e215e2ac1a1b9de7ddbc75e8286bcf7eacb8ef74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 7.3 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
0f26c327671aa448234ca6898de67db3cc7defca7947113934a12ca28a76a605
BLAKE2b-256 checksum
How to use checksums
d4ecc1ad7f9e382166b6d3bde9593ba6ed8993982329ac080501f29f32cb5cab
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL luckee_cli-0.1.20261102052119548-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 7.1 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
8d4699444e00eb4f8b9a2118c0004e262a9fecb76863c3b2f00b677a0351a667
BLAKE2b-256 checksum
How to use checksums
2ee0815c98756fc181148e884d358713f1b0ba7ae86c52f5c3ac6e41dc89cd0a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_11_0_arm64.whl

Download URL luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_11_0_arm64.whl
Size 890.3 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4b52e8090536869fd13417e9a78cb5ea897b577db2c0a3aff18ef2b3a3b57d3c
BLAKE2b-256 checksum
How to use checksums
e9134a265dce54fbbe16d40654e36540f7ceedcd2455f7fdf99adfe042edc387
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_10_9_x86_64.whl

Download URL luckee_cli-0.1.20261102052119548-cp311-cp311-macosx_10_9_x86_64.whl
Size 994.6 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
12a7c57cb35da3b9ba92592969967ebea5743f36254f443299f9947828500cda
BLAKE2b-256 checksum
How to use checksums
a0c96f0ba748a4ae1717de362f1095a598a1930bb297f2e65339043bd00ce7c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp310-cp310-win_amd64.whl

Download URL luckee_cli-0.1.20261102052119548-cp310-cp310-win_amd64.whl
Size 849.3 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
034436110ebccaf3fd7d91b5c8bca91047926bcb11417d3c113d39203fbe15bc
BLAKE2b-256 checksum
How to use checksums
54570507756d60d3c3c38ffeb24a8ff1d8d9c3559474ab0be0c670e1529320ed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 7.0 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
ab561abd6c274611364a2145e4b2c46340bdbf888aeb26e36f4a6e294deab312
BLAKE2b-256 checksum
How to use checksums
4536f8c5356a854457f9d2cf7a5a7a19037c9a2d49fa6434367a07dfe1f2f0d3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL luckee_cli-0.1.20261102052119548-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 6.8 MB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
9249e7aff3e338f87906ee1fb62a7887680317c6922325587b5d91629fd29be4
BLAKE2b-256 checksum
How to use checksums
2e828084d9a123a4911c8b3474337c8bcc2455bca94129d850e4432ee3a12d8a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_11_0_arm64.whl

Download URL luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_11_0_arm64.whl
Size 903.7 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
8244f7604ce8efec4f55968499779c4f27ab485b00167f8e966188652a880b0e
BLAKE2b-256 checksum
How to use checksums
64db57c57aa9cf7b2aa61541744983cde7c42a0cec6b2bb335554413b0fb72dc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_10_9_x86_64.whl

Download URL luckee_cli-0.1.20261102052119548-cp310-cp310-macosx_10_9_x86_64.whl
Size 1.0 MB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
a79a4cb4cf9f0ffd7617ee97f14b005030fdbdbc4629409addbacbd3113d8834
BLAKE2b-256 checksum
How to use checksums
563ab75772e1be25da2fff037251209cf98cabb05b7416d62d20c31d99bbec0a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Security for luckee-cli 0.1.20261102052119548

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.

Full provenance

All 15 files in this release have been uploaded with provenance metadata.

Select from 15 files

Attestation for luckee_cli-0.1.20261102052119548-cp312-cp312-win_amd64.whl

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 Nov 2, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release
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