eec5d5ebf8
feat(core): restore MessageBus optionality for soft migration (Phase 1) ( #15774 )
2026-01-04 19:59:35 +00:00
c0ccb22460
chore: cleanup old smart edit settings ( #15832 )
2026-01-02 22:28:28 +00:00
dcd2449b1a
refactor: deprecate legacy confirmation settings and enforce Policy Engine ( #15626 )
2025-12-29 19:22:42 +00:00
d236df5b21
Fix tool output fragmentation by encapsulating content in functionResponse ( #13082 )
2025-12-15 20:36:34 +00:00
217e2b0eb4
fix: similar to policy-engine, throw error in case of requiring tool execution confirmation for non-interactive mode ( #14702 )
...
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2025-12-15 18:34:27 +00:00
5411f4a667
feat(hooks): Hook Agent Lifecycle Integration ( #9105 )
2025-11-24 22:31:48 +00:00
64eb14ab11
Fix exp id logging ( #13430 )
2025-11-21 20:44:50 +00:00
99c5bf2e97
Remove useModelRouter experimental flag ( #13593 )
2025-11-21 17:54:17 +00:00
d1e35f8660
Protect stdout and stderr so JavaScript code can't accidentally write to stdout corrupting ink rendering ( #13247 )
...
Bypassing rules as link checker failure is spurious.
2025-11-20 10:44:02 -08:00
7bb13d1c41
telemetry: track interactive session state ( #12856 )
...
Co-authored-by: owenofbrien <86964623+owenofbrien@users.noreply.github.com >
2025-11-11 10:03:32 +00:00
19ea68b838
Refactoring packages/cli/src/ui tests ( #12482 )
...
Co-authored-by: riddhi <duttariddhi@google.com >
2025-11-03 18:10:57 +00:00
54fa26ef0e
Fix tests to wrap all calls changing the UI with act. ( #12268 )
2025-10-30 18:50:26 +00:00
13aa0148e7
Migrate tests to use avoid jsdom ( #12118 )
2025-10-28 17:32:15 +00:00
541eeb7a50
feat(core, cli): Implement sequential approval. ( #11593 )
2025-10-27 16:59:08 +00:00
ee66732ad2
First batch of fixing tests to use best practices. ( #11964 )
2025-10-25 21:41:53 +00:00
ce655436ef
fix(test): unskip and fix useToolScheduler tests ( #11671 )
2025-10-22 17:45:50 +00:00
b8df8b2ab8
feat(core): wire up UI for ASK_USER policy decisions in message bus ( #10630 )
2025-10-15 16:39:41 +00:00
0c3fcb7030
chore(mocktools): final step in unify mock tool definitions ( #9166 )
2025-09-29 20:43:06 +00:00
a0079785af
feat(telemetry): Add telemetry and metrics for model routing ( #8518 )
2025-09-16 20:53:58 +00:00
181898cb5d
feat(shell): enable interactive commands with virtual terminal ( #6694 )
2025-09-11 20:27:27 +00:00
dd23c77469
feat(core): Save large tool outputs to a file and return truncated lines ( #6240 )
2025-09-05 22:37:29 +00:00
044c3a0e14
Log config.useSmartEdit to Clearcut ( #7617 )
2025-09-03 09:58:47 +00:00
b5dd6f9ea6
feat(sessions): Integrate chat recording into GeminiChat ( #6721 )
2025-09-03 05:29:07 +00:00
45213103f6
chore(dedup): Mock tools refix ( #7418 )
2025-08-29 20:08:26 +00:00
5f16541c38
Revert "chore(cleanup): Consolidate MockTool definitions ( #7228 )" ( #7283 )
2025-08-28 04:06:50 +00:00
529c2649b8
Revert "Move mockTool into test-utils ( #7245 )" ( #7277 )
2025-08-28 03:05:47 +00:00
da7901acaf
Move mockTool into test-utils ( #7245 )
2025-08-27 20:18:15 +00:00
f0146c8b85
chore(cleanup): Consolidate MockTool definitions ( #7228 )
2025-08-27 18:18:26 +00:00
3e74ff71b7
feat(errors): Make errors more informative ( #7133 )
2025-08-26 23:22:05 +00:00
52dae2c583
feat(cli): Add --allowed-tools flag to bypass tool confirmation ( #2417 ) ( #6453 )
2025-08-26 16:17:43 +00:00
0f031a7f89
Explict imports & exports with type modifier ( #3774 )
2025-08-25 22:04:53 +00:00
75822d3506
Change the type of ToolResult.responseParts ( #6875 )
2025-08-22 21:12:05 +00:00
653267a64f
Remove unused attribute ( #6661 )
2025-08-20 23:13:50 +00:00
b561d3bbed
Log all session metadata ( #6423 )
2025-08-19 20:06:00 +00:00
1a2906a8ad
Revert #6088 ( #6328 )
2025-08-15 17:27:33 +00:00
8f2fa5a537
feat(core): Migrate MockTools to declarative pattern. ( #6197 )
2025-08-15 15:44:26 +00:00
980091cbc2
feat(core): refactor shell execution to use node-pty ( #6088 )
2025-08-14 20:40:12 +00:00
d3fda9dafb
Zed integration schema upgrade ( #5536 )
...
Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com >
Co-authored-by: Ben Brandt <benjamin@zed.dev >
2025-08-13 15:58:26 +00:00
6133bea388
feat(core): Introduce DeclarativeTool and ToolInvocation. ( #5613 )
2025-08-06 17:50:02 +00:00
dc2ac144b7
Various spelling improvements ( #3497 )
...
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com >
Co-authored-by: Sandy Tao <sandytao520@icloud.com >
2025-07-21 21:54:44 +00:00
761ffc6338
Zed integration ( #4266 )
...
Co-authored-by: Agus Zubiaga <agus@zed.dev >
Co-authored-by: Ben Brandt <benjamin.j.brandt@gmail.com >
Co-authored-by: mkorwel <matt.korwel@gmail.com >
2025-07-17 22:25:23 +00:00
23197151c2
Summarize tool call outputs using tool specific summarizers ( #3745 )
2025-07-11 16:29:08 +00:00
8d3fec08e5
Add and improve JSDoc comments for core tool methods ( #3128 )
2025-07-04 00:13:02 +00:00
f6c36f75e3
fix: prepublish changes to package names ( #1420 )
2025-06-25 12:41:11 +00:00
b443b5e800
Ensure telemetry events are flushed immediately ( #1344 )
...
The previous implementation used `flushIfNeeded` to batch most telemetry events, but it was not reliably sending them, leading to data loss. Notably, the `startSession` event, which already used `flushToClearcut`, was working correctly, indicating an issue with the batching logic itself.
This change replaces all calls to `flushIfNeeded` with `flushToClearcut` to align all event logging with the working `startSession` implementation and ensure that events are sent immediately. This prioritizes the reliability of data collection over network efficiency.
This is a temporary solution to prevent further data loss. The underlying issue with the batching mechanism in `flushIfNeeded` should be investigated and fixed in the future, at which point this change can be reverted.
2025-06-23 22:05:02 +00:00
98f3a7066e
refactor: rename disableDataCollection to dataCollectionEnabled ( #1319 )
...
Renames the `disableDataCollection` flag to the more intuitive and positive `dataCollectionEnabled`.
This change improves code clarity by avoiding double negatives and making the purpose of the flag more direct. The logic has been inverted wherever the flag is used to accommodate the new naming convention.
Using a suffix like `"Enabled"` follows a common convention that improves readability.
- A condition like `if (dataCollectionEnabled)` reads like a natural language sentence ("if data collection is enabled"), which reduces cognitive load.
- Distinguishes the boolean flag (representing a state) from potential functions that would perform an action (e.g., `enableDataCollection()` or `disableDataCollection()`), avoiding ambiguity between checking a value and calling a function.
#750
2025-06-23 21:19:40 +00:00
4cfab0a893
Clearcut logging - initial implementation ( #1274 )
...
Flag-guarded initial implementation of a clearcut logger to collect telemetry data and send it to Concord for dashboards, etc.
2025-06-22 14:26:48 +00:00
a2fee6bdd3
fix mcp timeouts and missing description on mcp errors ( #868 )
2025-06-08 21:52:11 -07:00
f2ea78d0e4
fix(tool-scheduler): Correctly pipe cancellation signal to tool calls ( #852 )
2025-06-08 22:42:49 +00:00
18d6a11c04
refactor: rename gemini-code to gemini-cli ( #822 )
2025-06-07 14:27:22 -07:00
Abhi