dev/gemini-cli - [no description]

Age	Commit message (Collapse)	Author
2025-05-30	Rename server->core (#638)	Tommaso Sciortino

2025-05-30	use json block for mcp tool output (and re-enable markdown rendering) (#635)	Olcan

2025-05-30	confirm mcp tool executions from untrusted servers (per "trust" setting) (#631)	Olcan

2025-05-29	Change Config to use named parameters. (#593)	Jacob Richman

2025-05-28	refactor: Extract MCP discovery from ToolRegistry	Taylor Mullen
	- Moves MCP tool discovery logic from ToolRegistry into a new, dedicated MCP client (mcp-client.ts and mcp-tool.ts). - Updates ToolRegistry to utilize the new MCP client. - Adds comprehensive tests for the new MCP client and its integration with ToolRegistry. Part of https://github.com/google-gemini/gemini-cli/issues/577
2025-05-17	ability to override core system prompt (via .gemini/system.md) and specify ↵	Olcan
	core tools via coreTools setting (e.g. coreTools:["ls", "GrepTool", ...]) ; added tests, but did not update docs for now (#413)
2025-05-17	added timeout setting to mcp server config, also switched to custom config ↵	Olcan
	type without "stderr" field that does not make sense in settings (#410)
2025-05-17	fix multiple mcp servers	olcan

2025-05-16	feat: Strip schema props from MCP tool definitions	Taylor Mullen
	- This change modifies the tool discovery process for MCP (Model Context Protocol) tools. - When tools are fetched from an MCP server, the `additionalProperties` and `$schema` fields are now recursively removed from their input schemas. This ensures cleaner and more concise tool definitions within the CLI, aligning with the expected schema structure and preventing potential conflicts or verbose outputs. - The corresponding tests in `tool-registry.test.ts` have been updated to reflect this new behavior and verify the correct stripping of these properties. Workaround for https://github.com/google-gemini/gemini-cli/issues/398
2025-05-16	GC "add tool registry tests"	Taylor Mullen
	- Ok