How memory carries over

Your memory, whatever saved instructions and preferences tAI has been asked to remember across conversations, carries over automatically between the browser and tCode, since both read from the exact same account.

Something you asked tAI to remember in a browser chat session is already available the very next time you start a session in tCode, with nothing to sync or reconfigure manually between the two.

/memory <request> run from inside tCode updates the same underlying memory the web app reads from, and the reverse is equally true, a change made from the browser is immediately visible from tCode as well.

This shared memory is account-level, not project-level or machine-level; something remembered while working in one project folder is available the next time you start tCode anywhere, not scoped to the specific folder it happened to be set from.

/memory with no argument lists what is currently saved, a fast way to check what tAI already knows about your preferences before assuming something needs to be re-explained.