Investigate if an in-memory scratchpad is a better solution for tracking the To-Do list

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
ai, tooling

Research direction

Start by reviewing the WriteTodo experiments in issue #48 and the referenced codebase-investigator.ts precedent. Compare the context and token trade-offs of tool calls versus an in-memory scratchpad, then document a recommendation and the implementation scope needed to adopt it.

Written by the indexing model from the issue text.

Description

We did run some experiments with the WriteTodo tool (https://github.com/gemini-cli-extensions/security/issues/48), but there is also some precedent from the Gemini CLI Code Investigator sub-agent (https://github.com/google-gemini/gemini-cli/blob/main/packages/core/src/agents/codebase-investigator.ts) to use just an in-memory scratchpad and avoid all those tool calls to pollute the context and spend extra tokens.

Dominant language
TypeScript
Stars
793
Forks
60
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemini-cli-extensions/security

All issues in gemini-cli-extensions/security

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.