codepraxis
Build CodePraxis questions in the same container a candidate gets, and save them to the platform as drafts.
pip install codepraxis
export CODEPRAXIS_API_KEY=... # dashboard → Settings → API keys
Then, in Claude Code:
/plugin marketplace add codepraxis-org/codepraxis-cli
/plugin install codepraxis@codepraxis
and run /codepraxis:plan, /codepraxis:build, /codepraxis:test,
/codepraxis:ship. The plugin drives the CLI below.
Commands
codepraxis push <q> save the question to the platform (a draft keeps one version)
codepraxis pull <q|id> get it back from the platform, solution included
codepraxis launch <q> [--fresh] open it in a container, the way a candidate gets it
codepraxis exec <q> "<command>" run a command there as the candidate (sends changes first)
codepraxis test <q> [--visible] Run, or the starter/solution check (sends changes first)
codepraxis logs <q> [source] setup, grader, exec, run or results
codepraxis categories the categories a public question can go into
codepraxis stop <q> hand the container back now
codepraxis install claude-plugin write the plugin into this repository instead
<q> is a folder under challenges/: a pack/ (and solution/) for a coding
question, or a question.json (and entities/) for an AI interview question.
Nothing runs on your machine. push saves the question to the platform as a
draft (a published question gets a new version); the reference solution is kept
privately. launch loads the pushed question into your container, where
setup.sh runs as it does for candidates and must finish within 2 minutes.
exec and test send your changed files to that container first, so each edit
is tried in seconds. A draft can be previewed but not assigned; publish it from
its page on the website.
Every command prints its stages: → started, ✓/✗ finished (with the time),
… while waiting (with what it is waiting for), and a final Next:.
CODEPRAXIS_API_URL points the CLI at another platform (default
https://www.codepraxis.co/api/public).
Release files for codepraxis 1.0.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 | |
|---|---|---|---|
| codepraxis-1.0.0.tar.gz | 51.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codepraxis-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 105.0 kB
Release files / codepraxis-1.0.0.tar.gz
| Download URL | codepraxis-1.0.0.tar.gz |
|---|---|
| Size | 51.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
527eef43d2cfb7c821eac8121815bae9c2f7f42723feee26e80728e6da6ca504
|
|
BLAKE2b-256 checksum How to use checksums |
0cb82816e7ecf30dcd55ac9e8f597b0de470bdae70f288b4a8f82390d95d12b9
|
| 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 Sep 26, 2026.
Transparency logRelease files / codepraxis-1.0.0-py3-none-any.whl
| Download URL | codepraxis-1.0.0-py3-none-any.whl |
|---|---|
| Size | 53.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
914e0d1faa4854cc0ab04dc3c52dbedbf0dcdf820e867869fe85f0d51d4d0085
|
|
BLAKE2b-256 checksum How to use checksums |
49b9905a66a336ce039c0a15d53acad648a7b48e74aebce64bb1aadf6273bcab
|
| 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 Sep 26, 2026.
Transparency log