Atelier
Atelier is a starter for research with coding agents. Keep the question, experiment, results, and conclusion linked in one Git repository. Agent work records give people a short summary and the next agent enough context to continue.
This is an early release; the file conventions are still being tested.
Try it
Requires Python 3.11+, uv, and Git. Create a project:
uvx create-atelier my-research --no-setup
cd my-research
uv sync
git add .
git commit -m "Initialize research project"
uv run --locked python experiments/exp-001/analyze.py
uv run python -c "import polars as pl; print(pl.read_parquet('experiments/exp-001/summary.parquet'))"
The example estimates a mean from synthetic observations. Inspect
experiments/exp-001/summary.parquet for how error changes with sample size.
The source revision and inputs are in
experiments/exp-001/provenance.json. This demonstrates the workflow; it makes
no claim about real-world systems.
For the optional figure, install Node.js 22+ and run npm install && npm run figure
inside my-research. Open figures/cache/mean.svg.
Omit --no-setup for a walkthrough that offers dependency installation, optional
figure tools, Hugging Face storage, and a first commit and push. Remote repositories
default to private; creation and upload require confirmation. Local work needs no
remote account. Resume with uvx --from create-atelier atelier setup ..
See the generated project's README for setup details.
Do your research
Start with docs/design.md: replace the example question with your hypothesis
and tasks. Use your editor or coding agent to change the experiment configuration
and analysis in experiments/exp-001/. Commit the inputs, run the experiment,
inspect its results, and link the evidence when proposing a conclusion in the
design document.
The generated AGENTS.md describes task claims, evidence, and review conventions.
Its skills guide writing, code design, and figures. For substantial work, keep
agents/work/<task>.md current: a TL;DR at the top, followed by an append-only
log of inputs, attempts, results, decisions, and next steps. Optional branch refs
and commit hashes link the work to its code changes. See work records.
The files remain usable without the generator or a particular frontend. Markdown holds documents; YAML holds configuration and discussions; Parquet holds tables. Each experiment records its inputs and source revision to help another person or agent reproduce it. See the file conventions when adapting the example.
Read and review
The browser reader opens an Atelier stored on Hugging Face. It shows documents, agent work, experiments, and figures without running repository code. The separate frontend package also reads local working trees and builds a static site.
Check a research project's files with:
uvx --from create-atelier atelier lint /path/to/research --programmatic
Omit --programmatic to add agent reviews of writing, code design, and figures.
Full review requires an authenticated Codex or Claude Code CLI and sends review
content through that CLI to its model provider. These checks
inspect the record; they do not establish that a scientific conclusion is true.
Lint neither runs the experiment nor applies fixes. See lint coverage and reports.
Develop Atelier
From a source checkout:
uv run python -m unittest discover -s tests
uv build
The generator lives in src/create_atelier/; generated files come from its
template/ directory. The independent frontend/ package has its own instructions
and tests.
Licensed under Apache-2.0. Generated projects include the license and attribution; vendored libraries retain their own licenses.
Metadata
Release files for create-atelier 0.1.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 | Actions |
|---|---|---|---|---|
| create_atelier-0.1.0.tar.gz | 329.5 kB | Without provenance | Details for create_atelier-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| create_atelier-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for create_atelier-0.1.0-py3-none-any.whl |
Total release size: 397.2 kB
Release files / create_atelier-0.1.0.tar.gz
| Download URL | create_atelier-0.1.0.tar.gz |
|---|---|
| Size | 329.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7e51e1c188c0f7141e556b4596f0b1c3979c6c8936842f1a0ee474acefc9ead
|
|
BLAKE2b-256 checksum How to use checksums |
f1134fd97fafee30fd308aece2b4e675f424b1b07b9e362647b49f8ab9e1339b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / create_atelier-0.1.0-py3-none-any.whl
| Download URL | create_atelier-0.1.0-py3-none-any.whl |
|---|---|
| Size | 67.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
adc5fa82913b32f020daf8082522770508f1f2e15eca71f4569dfd97c982b076
|
|
BLAKE2b-256 checksum How to use checksums |
63533eac0d4733aba1c6eba75c0b21b9e8fa5709584a26d25bc2b25584b1e39d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for create-atelier 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.