Hey 👋,
Some releases are about one big feature.
This one is about a few smaller breaks that add up when you're actually using the workflow.
If you're using imdone to keep story work close to the code, those breaks matter.
Launching the wrong HDD session matters.
Keeping provider secrets plain in .env longer than you want matters.
Trying to automate CLI workflows and getting messy structured output matters.
That's what I cleaned up in imdone 0.68.0.
Three changes carry most of the release:
- imdone hdd now prompts you to confirm or switch the target story when you don't pass an issue key, with your saved story preselected and a clean cancel path
- imdone init --1password can migrate Jira and GitHub credentials into 1Password directly, and normal imdone runs can resolve op://... references without the old wrapper-script path, so if you're using the wrapper today you can just use imdone directly now
- structured output is cleaner across pull, push, add, list, move, and test, which makes automation and AI-assisted workflows easier to trust
None of that is flashy.
But it does make the tool feel safer in the places where a little friction usually turns into hesitation.
That's the part I care about.
I want imdone to help teams keep shared context close to the code without making the surrounding workflow feel brittle.
If you want the full release details, the 0.68.0 section is here:
If you're using imdone already, I'd especially like to know which of these changes matters most to you:
- safer HDD startup
- direct 1Password support
- cleaner automation output
Reply and tell me where the workflow still feels heavier than it should.
Jesse
0 comments