stroblmeandClaude Opus 5 7c5b212f43 Let fluksio status read a local installation ...

`runs --local` already exists for the reason status needs it: the flows and the
history are in this directory, and looking at them should not need a server.
Watching still does — an in-process engine is the command itself, so nothing
could change under it — and says so rather than sitting on a still frame.

Found setting up a sandbox that drives the SDK entirely through --local.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019V5bsYGNxcgPs4xXmTPx69

2026-08-25 08:21:27 +02:00

..

alembic

Stage caching for batch runs, and an engine that lives in the command

2026-08-24 20:31:31 +02:00

api

Stage caching for batch runs, and an engine that lives in the command

2026-08-24 20:31:31 +02:00

cloud

Three fewer things to remember

2026-08-24 18:17:16 +02:00

core

Refuse what a node cannot publish, and stop timing out work that is fine

2026-08-25 07:30:14 +02:00

email-templates

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

flow

Add fluksio status, and ask for a run's parameters at a terminal

2026-08-25 07:42:09 +02:00

mcp

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

sdk

Let fluksio status read a local installation

2026-08-25 08:21:27 +02:00

__init__.py

Add a Python SDK: flows declared in your own repository

2026-08-23 20:16:08 +02:00

cli.py

Three fewer things to remember

2026-08-24 18:17:16 +02:00

crud.py

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

main.py

Stage caching for batch runs, and an engine that lives in the command

2026-08-24 20:31:31 +02:00

models.py

Stage caching for batch runs, and an engine that lives in the command

2026-08-24 20:31:31 +02:00

utils.py

Fix the CI gates: Python 3.13, concurrency groups, hook violations

2026-08-24 14:55:59 +02:00