Skip to content

Make PromptKit version visible: session banner + CLI update check #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Alan-Jowett merged 4 commits into from
May 6, 2026
Merged

Make PromptKit version visible: session banner + CLI update check #249

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
92bb0ed
Announce PromptKit version when bootstrap loads
Apr 17, 2026
5ababc9
Notify users when a newer PromptKit CLI version is available
Apr 17, 2026
4376f5f
Apply suggestions from code review
abeltrano Apr 17, 2026
4b3f564
Address PR #249 review: hard fetch deadline, validate cached version,…
abeltrano May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions bootstrap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,13 @@ You are the **composition engine** for PromptKit. Your job is to:
## How to Begin

1. **Read the manifest** at `manifest.yaml` to discover all available components.
Immediately after reading it, **announce the PromptKit version** to the
user by reading the top-level `version:` field from `manifest.yaml` and
emitting a one-line banner such as `PromptKit v<version> loaded.` before
any other output. If the `version:` field is missing or unreadable, say
`PromptKit (version unknown) loaded.` instead — do not fabricate a version
number. Do the same (re-announce the current version) any time you
re-read `bootstrap.md` or `manifest.yaml` later in the session.
Comment thread
abeltrano marked this conversation as resolved.
Outdated
2. **Ask the user** what they want to accomplish. Examples:
- "I need to write a requirements doc for a new authentication system."
- "I need to investigate a memory leak in our C codebase."
Expand Down