feat(examples): add automated setup scripts and fix statusline token display bugs#206
Open
weby-homelab wants to merge 38 commits into
Open
feat(examples): add automated setup scripts and fix statusline token display bugs#206weby-homelab wants to merge 38 commits into
weby-homelab wants to merge 38 commits into
Conversation
- Add README translations in Chinese, Spanish, French, Portuguese, Ukrainian, and German - Add a unified language switcher to all README variants to easily navigate between locales - Preserved identical code blocks, links, and layout structure across all variants
…ve README - Add official install scripts (install.sh, install.ps1, install.cmd) - Add Makefile with install/update/uninstall/check/run targets - Add .antigravity.md project config template - Add .gitignore for binaries and temp files - Rewrite README with full usage guide, configuration, migration from Gemini CLI Closes #0
feat: add install scripts, Makefile, config template, and comprehensive README
- Add manifests and binaries under the packages/ directory for all supported platforms - Modify install.sh, install.ps1, and install.cmd to prioritize local package files if present, facilitating instant and completely offline setups - Allow tracking of packages in .gitignore
- Centered badges, demo GIF, and title for a clean premium header section - Structured configuration guides with clear examples - Added modern callout boxes (Shields/GitHub alerts) - Kept ALT tags on all images for accessibility
feat: integrate pre-downloaded platform binaries for offline setup
docs: modernize README.md layout and styling
feat(install): migrate local binaries to release assets and update installers
fix(install): fix unbound DOWNLOADER variable in install.sh
…ad fork release assets
docs: resolve installer URLs and clarify offline setup in README
fix(install): point DOWNLOAD_BASE_URL to raw GitHub of fork to download fork release assets
docs: polish terminology and Ukrainian grammar in README.md
docs: add comprehensive legal disclaimers to README
feat: upgrade to v1.0.3 and add multi-language README support
docs: expand tagline and translate complete README into all supported languages
docs: correct settings.json path and schema fields
…ents schema in all READMEs
…-filename fix: correct workspace config filename to GEMINI.md and specialized agents schema
feat(statusline): enhance statusline with all documented fields
… current_usage object directly
fix: statusline context window token counts
… all statusline implementations
…ion for cross-platform scripts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces automated setup scripts for both custom statusline and custom window title examples, and provides new reference implementations for Fish, Node.js, and PowerShell.
Bug Fixes
It also fixes a critical type-mismatch bug present in all statusline implementations (statusline.sh, statusline.js, statusline.ps1, statusline.fish).
The Problem
The statusline scripts were checking if
.context_window.current_usageis greater than 0 to determine whether to render token count details. However, in the actual JSON payload emitted by theagyCLI,current_usageis a JSON object (containinginput_tokens,output_tokens,cache_read_input_tokens, etc.) rather than a number. This comparison failed silently across all platforms, leaving the token display section blank.The Solution
We updated the scripts to sum the total input and output tokens (
total_input_tokensandtotal_output_tokens) to calculate the context window usage. This resolves the object comparison issue and successfully restores the detailed token display in the TUI (e.g.(184.0K/1.0M · 141.3K in/41.9K out)).