Abhinav in #general: "Hi, when I work across a few chats in the same project, I keep re-telling the agent things that already came up in an earlier chat. right now the only..." | Archestra Community

#general

Jun 27June 29, 2026

Hi! I completed the contributor onboarding (PR #5754 was merged) for my account @ghorhh473-coder, but GitHub's interaction limit is still blocking me from opening new PRs because the merge commit was Co-authored. Could you please invite me as a collaborator so I can submit my bounty PRs?

ikshant Shukla12:03 PMOpen in Slack

anyone from team?

7 replies

Abhinav2:18 PMOpen in Slack

Hi, when I work across a few chats in the same project, I keep re-telling the agent things that already came up in an earlier chat. right now the only way to carry that context over seems to be editing the project instructions manually.

Is there any way for a project to "remember" facts that come up across its chats, or is the manual instructions file the intended approach? curious if per-project memory is something that's planned.

2 replies

Ghor Hh3:16 PMOpen in Slack

@Ildar Iskhakov @user Konstantinov Guys, actually I am Ghor Hh (who posted above at 11:32 AM). I am trying to submit my bounty PRs for @ghorhh473-coder but GitHub's interaction limit is blocking me because the onboarding PR #5754 was Co-authored. Could you please send me a collaborator invitation on GitHub so I can open the PRs?

13 replies

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!

Thread

Abhinav2:18 PMOpen in Slack

Is there any way for a project to "remember" facts that come up across its chats, or is the manual instructions file the intended approach? curious if per-project memory is something that's planned.

2 replies

Innokentii Konstantinov (archestra team)2:25 PMOpen in Slack

Hi! We are going to add memory in a next major release

Innokentii Konstantinov (archestra team)2:26 PMOpen in Slack

For now approach is to edit instructions manually or by asking an agent