jcode memory needs prompt to activate
Open
Nobody has claimed this yet.
enhancement
priority: medium
triage: needs-decision
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
I am enjoying Jcode so much! And today I figured that Jcode does not use it's memory functionality, if it is not told to do so. I figured today while watching the memory usage video at readme.md. And I opened a session and told jcode to activate it's memory and now it's doing the memory tool calling which it was doing so far.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior in a jcode session by using memory without explicitly asking to activate it, then compare it with the memory usage section in README.md. Trace where memory tool calling is enabled and verify that a normal session uses memory without the extra prompt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100