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.20261104114246562

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.20261104114246562
File Actions
luckee_cli-0.1.20261104114246562-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for luckee_cli-0.1.20261104114246562-cp312-cp312-win_amd64.whl
luckee_cli-0.1.20261104114246562-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.20261104114246562-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
luckee_cli-0.1.20261104114246562-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for luckee_cli-0.1.20261104114246562-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
luckee_cli-0.1.20261104114246562-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for luckee_cli-0.1.20261104114246562-cp312-cp312-macosx_11_0_arm64.whl
luckee_cli-0.1.20261104114246562-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.20261104114246562-cp312-cp312-macosx_10_13_x86_64.whl
luckee_cli-0.1.20261104114246562-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for luckee_cli-0.1.20261104114246562-cp311-cp311-win_amd64.whl
luckee_cli-0.1.20261104114246562-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.20261104114246562-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
luckee_cli-0.1.20261104114246562-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.20261104114246562-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
luckee_cli-0.1.20261104114246562-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for luckee_cli-0.1.20261104114246562-cp311-cp311-macosx_11_0_arm64.whl
luckee_cli-0.1.20261104114246562-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.20261104114246562-cp311-cp311-macosx_10_9_x86_64.whl
luckee_cli-0.1.20261104114246562-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for luckee_cli-0.1.20261104114246562-cp310-cp310-win_amd64.whl
luckee_cli-0.1.20261104114246562-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.17+ x86-64, Linux glibc 2.28+ x86-64 Details for luckee_cli-0.1.20261104114246562-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
luckee_cli-0.1.20261104114246562-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for luckee_cli-0.1.20261104114246562-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
luckee_cli-0.1.20261104114246562-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for luckee_cli-0.1.20261104114246562-cp310-cp310-macosx_11_0_arm64.whl
luckee_cli-0.1.20261104114246562-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.20261104114246562-cp310-cp310-macosx_10_9_x86_64.whl

Total release size: 50.3 MB

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

Download URL luckee_cli-0.1.20261104114246562-cp312-cp312-win_amd64.whl
Size 819.9 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
602fd5d575958fa0d6c0ce0525c360179d0aa0f25a63a5756b47260d925adfe7
BLAKE2b-256 checksum
How to use checksums
6ce8fb4206b2769a6c68208e14e1d3b0421e809ee83ae61aa8a8330392228473
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
2bffd61036518b9f6b0f6ca7936ad6010613207ad50e48d25fbd4b2d25566ec3
BLAKE2b-256 checksum
How to use checksums
ff6ab40e894456f26f1f9395ca2b5c2c3ff703574eeeb64134affe6571a381af
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
9c8e0d985bd677fe06e8f3fd5e52b232116fda1722fe349e9448908b7293df8d
BLAKE2b-256 checksum
How to use checksums
ef1148ca5bdc409af834054ff9e8e79ca5dd2f7df41779d467787dd06fc5f2e8
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-cp312-cp312-macosx_11_0_arm64.whl
Size 868.3 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
641bd93fcfec1567e12446f113d130d68e0090336e7ef02a7bb0f96ad1b09b89
BLAKE2b-256 checksum
How to use checksums
f260c56089eb491676b9a9a53341e731d2624e19c79ba408940d81a0b8999951
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
a3f377d80485b38af799a425adf17e1844cef864eaa33a4b1d185df0a139b1c0
BLAKE2b-256 checksum
How to use checksums
05125c68802536273ec90a5edc64ee4aa8b561a33cc98901f3e685551fe3970e
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-cp311-cp311-win_amd64.whl
Size 849.0 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
46c3712e98161c545ac881ba63fec7f184f8ef0adf46d4ad2adb6efea1f0097a
BLAKE2b-256 checksum
How to use checksums
ad68894db1d1fcfc91ae0593ee2052d64151550c57e2f2bd641e23078b2e0114
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
47ae748d9129b6c2382b78f14d1d5fc71490c63db11ee516fb729aefa4b57ff9
BLAKE2b-256 checksum
How to use checksums
49ac16da281351d4dfd03f513a76ca1a076b009dfb320049df9164d4301cffb9
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
487fe8842b2cb1acee884e6b75b9b3cee5787a2e8ac786be4142e32f258f154e
BLAKE2b-256 checksum
How to use checksums
b67b9e17126306843f1e7bac2910bf47e28cf01b37965c37c70f40582bf03090
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-cp311-cp311-macosx_11_0_arm64.whl
Size 890.2 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
43d0fe3f6cc238985265e841202fcb063bfae8c32d1fcdd392103c202ae0c850
BLAKE2b-256 checksum
How to use checksums
47636a5807fb12b86d2e76d10fb292e70012f43d1357a1350c28fa77930f36ec
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
fe778550fb17767e3f25a05931b74da4960888b4439a7fb5eb4be4bd7b05d1f8
BLAKE2b-256 checksum
How to use checksums
1f34a4680002512cf3c6a46c5f8c304dc44a192d58878094b19915b25f639df5
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-cp310-cp310-win_amd64.whl
Size 849.3 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
2cbb496323d3277c09c258b1d595f7478d7e8e906cfc994e455b39e670bacee7
BLAKE2b-256 checksum
How to use checksums
46518bdb77e8246963f8f4d0064e1fb51b61f4c9c18cc2cbf925b5ac8b184f17
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
dc80889cd846fdc73817f8ba50a0281618f86f70d29a824901d0fe543e111bbc
BLAKE2b-256 checksum
How to use checksums
c0368866ca31b201635c26e978e229e76b317c87b2d45a527e9c06a6044c8991
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
a2f37ecebcec18131fb0bd93f19d14b6e16fc56b3d3056ccbc9025b0ef560dc5
BLAKE2b-256 checksum
How to use checksums
08c6c8d0fedc834a7d56fc0a7748daf6142cc911042fc8d9e6f8b1aadeeadaf8
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
e5d058547c6fb41a1329a2b84fa07b69b412c38f6d2d8b9b74b61fee88c248c0
BLAKE2b-256 checksum
How to use checksums
23681ed82a376d5d9d8e1bc8f5913717588b0ff0730c5db22ffc977f98587dca
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 4, 2026.

Transparency log

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

Download URL luckee_cli-0.1.20261104114246562-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
1e0ceb8d59e34493cdba9e95439eee92e3870ff2e6d5adc41c4aea83582a774b
BLAKE2b-256 checksum
How to use checksums
548cbfc27b21093a405b1c1124543133978ff6f5b352292a061e8aeb8754a2d5
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 4, 2026.

Transparency log

Security for luckee-cli 0.1.20261104114246562

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.20261104114246562-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 4, 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