Code Craft AI TimeTravel Server
The codecraftai-timetravel-server package is a web service that provides a web interface for the codecraftai-timetravel-pod package. It is built on the codecraftai-webservice-flask stack and offers trace reception, persistence, remote debug control, and a web UI for time-travel debugging of instrumented applications.
Highlights
Persistence and data foundation: ORM models, credential store, server configuration model, and pluggable trace-data storage backends.
Process lifecycle: service registration, unregistration, heartbeat reception, and a persistent process registry.
Remote debug control: portal discovery, activation/deactivation, trace-configuration management, and debug-session coordination.
Trace data reception: TCP and Unix-socket stream receivers, hybrid-format deserializer, back-pressure, and stream multiplexing.
REST API and web UI: process management, portal control, trace configuration, debug sessions, and timeline/call-graph/variable views.
Authentication, authorization, TLS, audit logging, and operational concerns (migrations, metrics, retention, graceful shutdown).
Repository Structure
development/ - Runtime environment scripts.
repository-setup/ - Repository homing and setup scripts.
source/packages/ - Package source code.
source/site/ - Flask site and web UI assets.
source/testroots/ - TestBase test roots.
specs/ - Requirements and design documentation organised by feature layer.
Environment Setup
When working in a Codex container:
./development/setup-agent-container
For local development:
./repository-setup/rehome-repository
./development/setup-envrionment
Running Tests
Activate the virtual environment:
source .venv/bin/activate
Run the single-host test suite:
testbase testing run --root source/testroots/ccai --includes=ccai.tests.singlehost.timetravelserver --output=./.output
Standards and Conventions
Feature specifications under specs/ are organised by layer (s0-* persistence, s1-* process lifecycle, s2-* remote control, and so on).
Additional Resources
Feature specification folders under specs/ define each server subsystem in detail.
Metadata
Release files for codecraftai-timetravel-server 1.3.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 | Provenance | |
|---|---|---|---|---|
| codecraftai_timetravel_server-1.3.0.tar.gz | 36.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codecraftai_timetravel_server-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 89.1 kB
Release files / codecraftai_timetravel_server-1.3.0.tar.gz
| Download URL | codecraftai_timetravel_server-1.3.0.tar.gz |
|---|---|
| Size | 36.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5480f25e7f611579ee8049c5d9541ff3dcba33cf888e73f52b7174f2e143c718
|
|
BLAKE2b-256 checksum How to use checksums |
dbdb4b942ac4c3209565482fe296c137fa87101e93c8019670780e9951a5edda
|
| 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 Oct 19, 2026.
Transparency logRelease files / codecraftai_timetravel_server-1.3.0-py3-none-any.whl
| Download URL | codecraftai_timetravel_server-1.3.0-py3-none-any.whl |
|---|---|
| Size | 53.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a278a638207b972abd5b31bcca09aaac04efb68b70f6946a2fb73b824beae9e3
|
|
BLAKE2b-256 checksum How to use checksums |
bdcc442bec0c40ff8723113b829414ca565972422d3f454aed537295b8eb72db
|
| 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 Oct 19, 2026.
Transparency logSecurity for codecraftai-timetravel-server 1.3.0
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 2 files in this release have been uploaded with provenance metadata.
Attestation for codecraftai_timetravel_server-1.3.0.tar.gz
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 Oct 19, 2026.
Transparency logA 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.