ef4329a708
policy: extract legacy policy from core tool scheduler to policy engine ( #15902 )
2026-01-07 04:28:06 +00:00
8a2eddcb25
feat(core): restore MessageBus optionality for soft migration (Phase 1) ( #15774 )
2026-01-04 19:59:35 +00:00
5ab0c5d33d
chore: cleanup old smart edit settings ( #15832 )
2026-01-02 22:28:28 +00:00
895ca9eb3f
refactor: deprecate legacy confirmation settings and enforce Policy Engine ( #15626 )
2025-12-29 19:22:42 +00:00
13e1ebcef9
Fix tool output fragmentation by encapsulating content in functionResponse ( #13082 )
2025-12-15 20:36:34 +00:00
37e9bf8a11
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
67e001eccd
feat(hooks): Hook Agent Lifecycle Integration ( #9105 )
2025-11-24 22:31:48 +00:00
f8ebe0fa6a
Fix exp id logging ( #13430 )
2025-11-21 20:44:50 +00:00
47f626aaac
Remove useModelRouter experimental flag ( #13593 )
2025-11-21 17:54:17 +00:00
9409be8e1b
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
bfcb4f883c
telemetry: track interactive session state ( #12856 )
...
Co-authored-by: owenofbrien <86964623+owenofbrien@users.noreply.github.com >
2025-11-11 10:03:32 +00:00
6234884dc9
Refactoring packages/cli/src/ui tests ( #12482 )
...
Co-authored-by: riddhi <duttariddhi@google.com >
2025-11-03 18:10:57 +00:00
565ac50ddc
Fix tests to wrap all calls changing the UI with act. ( #12268 )
2025-10-30 18:50:26 +00:00
8edec7612e
Migrate tests to use avoid jsdom ( #12118 )
2025-10-28 17:32:15 +00:00
2cb02da5b2
feat(core, cli): Implement sequential approval. ( #11593 )
2025-10-27 16:59:08 +00:00
58cf2f076a
First batch of fixing tests to use best practices. ( #11964 )
2025-10-25 21:41:53 +00:00
2ab9cd6171
fix(test): unskip and fix useToolScheduler tests ( #11671 )
2025-10-22 17:45:50 +00:00
9d9e310682
feat(core): wire up UI for ASK_USER policy decisions in message bus ( #10630 )
2025-10-15 16:39:41 +00:00
d75c094d4f
chore(mocktools): final step in unify mock tool definitions ( #9166 )
2025-09-29 20:43:06 +00:00
81cb042da7
feat(telemetry): Add telemetry and metrics for model routing ( #8518 )
2025-09-16 20:53:58 +00:00
dc7656af8c
feat(shell): enable interactive commands with virtual terminal ( #6694 )
2025-09-11 20:27:27 +00:00
13c1efeb29
feat(core): Save large tool outputs to a file and return truncated lines ( #6240 )
2025-09-05 22:37:29 +00:00
e795f398fb
Log config.useSmartEdit to Clearcut ( #7617 )
2025-09-03 09:58:47 +00:00
c88afaa5f5
feat(sessions): Integrate chat recording into GeminiChat ( #6721 )
2025-09-03 05:29:07 +00:00
cb840e6c09
chore(dedup): Mock tools refix ( #7418 )
2025-08-29 20:08:26 +00:00
87c3cbb12a
Revert "chore(cleanup): Consolidate MockTool definitions ( #7228 )" ( #7283 )
2025-08-28 04:06:50 +00:00
2b206e9c56
Revert "Move mockTool into test-utils ( #7245 )" ( #7277 )
2025-08-28 03:05:47 +00:00
3bd7ffca66
Move mockTool into test-utils ( #7245 )
2025-08-27 20:18:15 +00:00
0c02a04cfd
chore(cleanup): Consolidate MockTool definitions ( #7228 )
2025-08-27 18:18:26 +00:00
15c92fa946
feat(errors): Make errors more informative ( #7133 )
2025-08-26 23:22:05 +00:00
2919b44546
feat(cli): Add --allowed-tools flag to bypass tool confirmation ( #2417 ) ( #6453 )
2025-08-26 16:17:43 +00:00
a97a6cc71b
Explict imports & exports with type modifier ( #3774 )
2025-08-25 22:04:53 +00:00
bcd4abcbd7
Change the type of ToolResult.responseParts ( #6875 )
2025-08-22 21:12:05 +00:00
0cd77d919d
Remove unused attribute ( #6661 )
2025-08-20 23:13:50 +00:00
e581285089
Log all session metadata ( #6423 )
2025-08-19 20:06:00 +00:00
1accf61de8
Revert #6088 ( #6328 )
2025-08-15 17:27:33 +00:00
5a7b3ddf74
feat(core): Migrate MockTools to declarative pattern. ( #6197 )
2025-08-15 15:44:26 +00:00
bb1da420ff
feat(core): refactor shell execution to use node-pty ( #6088 )
2025-08-14 20:40:12 +00:00
c00193b026
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
81c8e0163c
feat(core): Introduce DeclarativeTool and ToolInvocation. ( #5613 )
2025-08-06 17:50:02 +00:00
03f7b220d3
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
6e762dc70c
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
e97f349fc9
Summarize tool call outputs using tool specific summarizers ( #3745 )
2025-07-11 16:29:08 +00:00
c8ba3d1016
Add and improve JSDoc comments for core tool methods ( #3128 )
2025-07-04 00:13:02 +00:00
5ad4a0a826
fix: prepublish changes to package names ( #1420 )
2025-06-25 12:41:11 +00:00
463797730e
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
5ae029009b
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
a230beb945
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
0ab24b8191
fix mcp timeouts and missing description on mcp errors ( #868 )
2025-06-08 21:52:11 -07:00
07362d3163
fix(tool-scheduler): Correctly pipe cancellation signal to tool calls ( #852 )
2025-06-08 22:42:49 +00:00
Abhi