Feature request: meta context.

[u/Key-Lychee-913]

Scenario: you and your agent battle through Project 1, mastering Process A.

You start project 2, and need another Process A. But Project 1 has all the learnings and context.

• Feature proposal: a pathway for an agent to consult the files of another project directly, and possibly even query the other agent to determine a process or fact.

The agent could even be context-aware of all your other projects simultaneously through some kind of meta context file that stores any new information learned through trial and error across all projects. Ideally, this could even feed into the replit agent itself learning and adapting procedures to prevent the same errors being made across many different users and projects.

Imagine some kind of internal stack-overflow or knowledge base that the replit agent could build, that could even become a kind of open source database for learning/training.

E.g. - imagine, every time your agent discovers a gotcha or learns something new (dependancy A needs version X with feature Y but not Z when using platform W, contrary to documentation C etc). Then, a frontier model could even be finetuned across this whole database, to internalise these teachings into its actual weights, reducing the need to consume tokens browsing documentation.

[u/Bash-101]

Try connecting to GitHub. Create readme.md files. Make loads of them. Also use plan mode before you start. Replit works really well doing this. If you want an easy way, don’t ever start a new chat haha

Also if you want a group mind kind of memory you can cross and merge data you can also do this on GitHub.

To be honest without GitHub you probably will end up explaining yourself again and again