Thank you, that means a lot! I tried to make the caching behavior as transparent as possible so folks don’t have to dig through the code to figure out where things live. Really glad it helped, and happy to take suggestions if anything could be clearer.
Sorry for the delay, I missed this! Great question. The guess cache is local by default, but you can set ELF_CACHE_DIR to point it at a shared folder like iCloud, Dropbox, Google Drive, or anything that syncs across your machines. That will keep your guess history unified so you do not risk resubmitting a too low or too high answer. Happy puzzle solving!
Thanks! Caching around inputs and submissions was a priority to keep the workflow fast and predictable. Happy to hear any feedback if you try it out. Really appreciate it, and happy puzzle solving!
Happy to answer any questions about design choices, caching strategy, the guardrails for safe submissions, or anything else. If anyone uses AoC in a team or automation setup, I’m especially interested in what features would help.
I built a small CLI tool called elf to make Advent of Code workflows simpler. It helps with input fetching and caching, safe answer submission, viewing your progress, and reading private leaderboards.
Features
• input fetching with caching
• guardrails to prevent duplicate or invalid submissions
• private leaderboard viewer in table json or model formats
• status calendar and guess history viewer
• optional Python API for scripting