Releases: InsForge/CLI
Releases · InsForge/CLI
v0.1.54
What's Changed
- INS-73 fix(link): clearer error when user can't access project by @tonychang04 in #76
Full Changelog: v0.1.53...v0.1.54
v0.1.53
v0.1.52
v0.1.50
Non-TTY shell support
CLI no longer crashes with uv_tty_init EINVAL when run from agent shells (Claude Code, Cursor bash tools) or other non-TTY environments.
- New
src/lib/prompts.tsabstraction: clack in TTY (unchanged human UX), readline-backed fallback in non-TTY - OAuth flow prints the authorize URL prominently via stderr in non-TTY so agents can relay it to the human without polluting
--jsonstdout - Empty-options guard on non-TTY select prevents infinite loops
- Password prompts preserve whitespace
Merged via #67.
v0.1.49
What's Changed
- fix(link): polished "What's next" block — numbered, colorized, single copy-paste command by @tonychang04 in #65
Full Changelog: v0.1.48...v0.1.49
v0.1.48
v0.1.47
Fixes
link --templatenow installs agent skills inside the project directory. Previously the skills (.claude/,.codex/,.cursor/, …) were dropped in the parent cwd before the user was prompted for a subdirectory name, so they ended up one level above the actual project. New flow: prompt for directory → mkdir/cd → download template → npm install → install skills → report usage → show next steps.- Suggested prompt nudge. The third "Start building" prompt now reads "Build an AI chatbot with conversation history and deploy it to a live URL" so first-time users see the full build-and-ship flow.
v0.1.46
Fixes
- Actionable network errors.
fetch failedand generic exec errors are now classified with their root cause (DNS, ECONNREFUSED, timeout, TLS interception, permission, disk full, npm auth, 404, etc.) viaformatFetchErroranddescribeExecError. Users see what to fix, not a generic "try again". cli.linkevent now fires on--template. PreviouslyreportCliUsagebailed because project config wasn't yet on disk in the cwd when--templatewas used; it now accepts an explicit config passed from the link command.
Chores
- Added unit tests for the error formatters and
reportCliUsage. npm run lintnow runs vitest before eslint, so CI and publish workflows gate on tests in a single step.
v0.1.45
What's Changed
- INS-51: Support PostHog A/B testing in new onboarding by @CarmenDou in #61
Full Changelog: v0.1.44...v0.1.45
v0.1.44
What's Changed
Features
- Create command UX improvements — auto-select single org, project subdirectory support, better next steps messaging (#60)
- Link command template & deploy support —
--templateflag, suggested prompts for raw link, concise template flow (#58)
Fixes
- Prevent double config save, gate on template success
- Clean up project directory on setup failure
- Refined post-create messages for blank projects and templates
- Org auto-select in JSON mode, directory validation improvements
Full Changelog: v0.1.43...v0.1.44