| Age | Commit message (Collapse) | Author |
|
|
|
- We now have CI/CD
- We have linting support (so added a section)
- Fixed `npm run debug` to allow debugging again.
|
|
|
|
- There were a few hiccups here. Somehow 2.5-flash wasn't actually abiding by our tool schema. Instead it was inferring `path`. To semi-combat this I've renamed `file_path` -> `path`.
- We weren't elevating errors that were created via schema validation. Instead both the `glob` and `read-file.ts` now surface this.
- In error scenarios (like failing schema) we were improperly surfacing these as success cases because we were overriding tool status.
|
|
|
|
and fix missing license headers while we're here) (#62)
|
|
|
|
error handling in bash scripts (#63)
#61
|
|
|
|
|
|
|
|
|
|
* Wire through passthrough commands
* Add default passthrough commands
* Clean up config passing to useGeminiStream
|
|
* refactor: clean up build output
* refactor: add index.ts to package roots
|
|
* Adds debug mode config flag.
* Wire through debug lines
* Add debug mode logging example
* Run format
* Run format again
|
|
scripts/build_container.sh, then start with scripts/start_container.sh. Exit with ^C for now. (#61)
|
|
|
|
- This utilizes `ink-gradient` to render GEMINI CODE in amazing colors.
- Added a shared color configuration for UX (should this be in config?). It's very possible that we shouldn't be talking about the specific colors and instead be mentioning "foreground"/"background"/inlineCode etc. type colors.
- Updated existing color usages to utilize `Colors.*`
Fixes https://b.corp.google.com/issues/411385593
|
|
* Starting to move a lot of code into packages/server
* More of the massive refactor, builds and runs, some issues though.
* Fixing outstanding issue with double messages.
* Fixing a minor UI issue.
* Fixing the build post-merge.
* Running formatting.
* Addressing comments.
|
|
|
|
|
|
* Command line flags got broke. Now to run with flags run:
npm run start -- -m model-id -d data/dir
* Add *.tsbuildinfo to git ignore.
|
|
Up and down arrows traverse the command history.
|
|
|
|
|
|
|
|
Also fix the bug where the API key is used accidentally as the model name.
|
|
|
|
* Bump the character limit to web fetch.
* Piped Input Hook. First step in bringing in STDIN piping.
* Fix linting errors.
* Remove incorrect comment.
|
|
npm run start -- -m model-id -d data/dir
|
|
|
|
|
|
|
|
- Also updated ci.yml to ensure that linting failures will break the build.
Fully fixes https://b.corp.google.com/issues/411384603
|
|
|
|
- This has the entirety of the changes.
Part of https://b.corp.google.com/issues/411720532
|
|
Fixes https://b.corp.google.com/issues/411720532
|
|
|
|
- More changes are to come, this is truly a partial change in order to not disrupt as many people as possible.
Part of https://b.corp.google.com/issues/411384603
|
|
* Add a warning about the flickering in iTerm.
* Move the iterm warning out of App.tsx.
|
|
|
|
|
|
* Adding some wiring to allow the Ink app to warn if there are local development changes that haven't been captured in the recent build of the Gemini CLI.
* Adding a new useAppEffects.ts file that wores some useEffect handlers in.
* Updating package-lock.json to resolve `npm ci` issues.
* Updating package-lock.json and package.json to resolve `npm ci` issues.
|
|
* Adding a web fetch tool.
|
|
* feat: initial configs for npm publishing
* fix: workspace reference
* fix: include LICENSE in npm run build
|
|
- More changes are to come, this is truly a partial change in order to not disrupt as many people as possible.
Part of https://b.corp.google.com/issues/411384603
|
|
We don't have a use case for them yet.
|
|
* Introduce a config module to manage configuration
* Remove public modifier
|
|
Methods should be verbs. Fixes #4.
|
|
- As part of this work I also started building out errors.ts which will be a cumulation of error helpers to better handle the challenging `catch (error: unknown)` requirement.
- More changes are to come, this is truly a partial change in order to not disrupt as many people as possible.
Part of https://b.corp.google.com/issues/411384603
|