Memory

Memory gives agents persistent context that survives across sessions. Instead of re-explaining your project's conventions every time, you teach the agent once and it remembers.

Two types of memory

MEMORY.md — long-term knowledge

A single markdown file per project, injected into the agent's system prompt at the start of every session. Use it for things every agent should know:

• Project conventions and coding patterns
• Architecture decisions
• Your preferences ("always use Tailwind, never CSS modules")
• Important file paths

When you ask the agent to "remember this," it overwrites MEMORY.md with a complete updated version.

Daily logs — session-by-session notes

Date-stamped, append-only files (e.g. 2025-01-15.md). The last two days of logs are included in agent context at session start. Use them for:

• What got done in a session
• Decisions and trade-offs made
• Bugs found and fixed

The agent appends to daily logs automatically. Older entries are never modified.

Storage

~/.onestart/memory/{project-name}/MEMORY.md
~/.onestart/memory/{project-name}/{YYYY-MM-DD}.md

Browse memory files in the Memory section of the left sidebar.

Tips

• Keep MEMORY.md concise. It's injected into every session's context window, so bloated memory wastes tokens.
• Use daily logs for ephemeral details. They naturally age out as only the last two days are loaded.
• Review periodically. Remove outdated information so agents don't act on stale context.