The walkthrough's memory step never writes its lines
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 87/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- ai-infra-agents
Research direction
Read modules/memory.js and the walkthrough's shed step in apps/client/tutorial.js. Follow how the plain thread is created and how memory is enabled, then compare that with the endpoint evidence in the issue. Done means loading the example thread makes its memory lines appear as the walkthrough promises.
Written by the indexing model from the issue text.
Description
The Memory section says "Watch the lines get written, from the messages up." Load the example thread, ask about the shed, and the lines stay "being written, from the messages up" for good. The agent answers by reading all 34 messages, so memory isn't doing what the page shows it doing.
Right: loading the example thread makes its lines appear, as the section promises.
Evidence, fresh server, no bots:
$ curl -s localhost:3917/api/threads/187 | grep -o '"memory":[a-z]*'
"memory":false
$ curl -s localhost:3917/api/threads/187/memory | head -c 120
{"lines":[{"id":0,"n":1,"text":"(not summarized yet: zoom it)"},{"id":1,...
modules/memory.js:10: a thread without a bot doesn't remember unless switched on. The walkthrough's shed step (apps/client/tutorial.js:166) creates a plain thread with no bot and never switches memory on. Since 80e035c (memory on only where a bot is), this step can't work.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 14m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from oskarrough/agent-ide
-
scout
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
oskarrough/agent-ide#50 ·
-
scout
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
oskarrough/agent-ide#49 ·
-
scout
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
oskarrough/agent-ide#43 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
oskarrough/agent-ide#46 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
oskarrough/agent-ide#45 ·
All issues in oskarrough/agent-ide
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nearform/unbreakci#897 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
automation chore ci-cd consistency developer-experience difficulty: easy discoverability documentation enhancement github-actions good first issue help wanted hygiene priority: P3 seo shell yaml
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
swc-project/swc-next-issues#394 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#5790 ·
Maintainers usually reply within 1 day