This release is a pre-release and may not be stable for production use.
Dandy
A powerful open-source Python framework that simplifies the development of artificial intelligence software.
Get Started
Start by installing with pip install dandy and then checking out our quick start guide for more steps.
Documentation
Check out the Dandy Website for documentation including tutorials and more.
Command Line
The dandy command runs the coding assistant against the current project. Run it from your project root (where dandy_settings.py lives). If no dandy_settings.py exists, dandy will instead load settings from a dandy.json file found in .dandy/dandy.json in the current directory, or ~/.config/dandy/dandy.json as a last resort before creating a settings file for you.
dandy # start an interactive agentic loop
dandy "fix the failing tests" # run one request, then exit
dandy -r "one more fix" # run one request inside the latest session
dandy -s my-session "resume me" # run one request inside a named session
dandy -n new-name # start a fresh, pre-named conversation
dandy --sessions # list saved sessions
dandy --init # create or refresh the project AGENTS.md
dandy -d old-session # delete a saved session
dandy -h # show usage
Inside the interactive session every message goes to the coding agent. /new (or /n) starts a fresh conversation, /sessions (or /s) lists or resumes saved sessions, and pressing escape twice (or /quit) exits the loop. Use the one-shot form when you only want a single answer without entering the REPL.
The CLI's model is set with CLI_CONFIG in dandy_settings.py, e.g. CLI_CONFIG = {'CODING': 'DEFAULT'} points the coding agent at the DEFAULT entry in LLM_CONFIGS.
The same settings can be expressed as JSON when you don't want a Python module. Keys are case-insensitive at the top level (llm_configs === LLM_CONFIGS), so a minimal .dandy/dandy.json looks like:
{
"llm_configs": {
"default": {
"host": "api.example.com",
"api_key": "your-key",
"model": "your-model"
}
},
"cli_config": {"coding": "default"}
}
Metadata
Release files for dandy 3.0.0a6
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 |
|---|---|---|---|---|
| dandy-3.0.0a6.tar.gz | 131.7 kB | Without provenance | Details for dandy-3.0.0a6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dandy-3.0.0a6-py3-none-any.whl | Python 3 | none | any | Details for dandy-3.0.0a6-py3-none-any.whl |
Total release size: 322.6 kB
Release files / dandy-3.0.0a6.tar.gz
| Download URL | dandy-3.0.0a6.tar.gz |
|---|---|
| Size | 131.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
290ba1ea6f294a693c7873faf2ca938a89214e0bad2a88d54d37baa8c2b660b8
|
|
BLAKE2b-256 checksum How to use checksums |
71e172486a5b09d37280b9a9dd8be94ebdab6d8442639239fa55b348d6c3afbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / dandy-3.0.0a6-py3-none-any.whl
| Download URL | dandy-3.0.0a6-py3-none-any.whl |
|---|---|
| Size | 190.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df64a66a30a01b2ea04d879d7cc87766f5629119082a17dd26300602f3768008
|
|
BLAKE2b-256 checksum How to use checksums |
13bed1ed301221abb1eee464d2eb9ee9173abc53caa0208e2e6df34243e0dd47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Security for dandy 3.0.0a6
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.