Tries — On-demand project directories
A command-line tool for managing experimental projects. Centralizes temporary work with auto-dating, fuzzy search, and git integration. Originally a python port of tobi/try.
The problem
cd ~/Desktop && mkdir rds-test && cd rds-test
# ... do stuff ...
# 3 weeks later: where did it go?
find ~ -type d -name "*redis*" 2>/dev/null # Lost in the chaos
The solution
try redis # Jump to ~/.tries/experiments/2025-11-30-redis (create if missing)
# ... do stuff ...
# 3 weeks later... # Fuzzy match ~/.tries/experiments/2025-11-30-redis !
try rd
Features
- Centralized — All experiments in
~/.tries/experiments(configurable) - Auto-dated —
YYYY-MM-DD-nameformat for chronological sorting - Fuzzy search —
rdsmatchesredis-server,connpoolmatchesconnection-pool - Recency ranking — Recently used dirs float to top
- Git-first — Clone repos or create worktrees seamlessly
- Templates — Register reusable project scaffolds (remote or local)
- Dashboard —
try statsshows disk usage, oldest/newest, top experiments - Interactive TUI — Real-time filtering, keyboard nav
- Shell integration — Works with Bash/Zsh/Fish (enables
cdon selection) - Configuration —
~/.tries/config.jsonfor experiments dir, templates, etc. - Non-destructive — You control deletions
Quick start
Install
uv tool install tries
Enable shell integration
Add to ~/.bashrc or ~/.zshrc:
eval "$(try init)"
Fish:
try init fish | source
Then reload your shell.
Usage
try # Browse all experiments
try redis # Jump/create redis project
try new feature-xyz # Create "YYYY-MM-DD-feature-xyz"
try new api --template python # Create with template
try clone <repo-url> # Clone into dated directory
try . [name] # Create worktree from current repo
try stats # Show dashboard (size, count, oldest/newest)
try template list # List registered templates
try template add python --url <url> # Register remote template
try template add local --path ~/templates/my-template # Register local template
try --help # Show help
In the TUI
Search: redis
↓ 2025-11-30-redis-server [95%]
2025-11-20-redis-test [82%]
Keys: ↑/↓ navigate, Enter select, Ctrl-D delete, ESC cancel
Configuration
Experiments are stored in ~/.tries/experiments by default. Customize via ~/.tries/config.json:
{
"experiments_dir": "~/my-experiments",
"templates": {
"python": {
"url": "https://github.com/user/python-template"
},
"nextjs": {
"path": "~/templates/nextjs"
}
}
}
Priority for experiments directory:
TRY_PATHenv var (if set)experiments_dirin config.json- Default:
~/.tries/experiments
Development
git clone https://github.com/ajac-zero/try.git && cd try
uv sync
uv run pytest tests/
uv run ruff check && uv run ruff format
Metadata
Release files for tries 0.2.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 |
|---|---|---|---|---|
| tries-0.2.0.tar.gz | 12.5 kB | Without provenance | Details for tries-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tries-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for tries-0.2.0-py3-none-any.whl |
Total release size: 28.1 kB
Release files / tries-0.2.0.tar.gz
| Download URL | tries-0.2.0.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34e67d73b14064c8ae59358ffaf3893bed0154bde4f710b605a9dafd4a558a34
|
|
BLAKE2b-256 checksum How to use checksums |
576d33e2d080517be59b4c745e10e67880a4dc5b1bccfab496d045f935d6cd9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.5
|
Release files / tries-0.2.0-py3-none-any.whl
| Download URL | tries-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc049f5bfce3886ba3eafd052380d4b905ff9fc210061f698a459ba1b0da8f78
|
|
BLAKE2b-256 checksum How to use checksums |
1f98abe7828d55d524710885a2f767e46d46deb7ab425477ddc836a1264fea16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.5
|
Security for tries 0.2.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.