Session context keeps getting lost when switching between projects — how to maintain state?

[BittuChan]

Running goose CLI and noticed that when I switch directories or start a new session, it completely forgets the context from previous work. I was debugging a React component issue, stepped away for lunch, came back and started goose again in the same directory, had to re-explain the entire problem from scratch.

Is there a way to persist session context or resume where I left off? Working on a multi-day refactoring project and having to rebuild context every time is killing productivity.
Current workflow:

cd my-project
goose
# work for a bit
# close terminal
# later...
goose  # starts fresh, no memory

Am I missing a flag or config option?

[Shiven0504]

Hello @BittuChan, Goose sessions are ephemeral by design, each goose invocation starts fresh. However, there are a few workarounds:

1. Use the same terminal session -
   Don't close the terminal. Goose maintains context within a single session. If you need to step away, just minimize it.
2. Session summaries -
   Before closing, ask goose: "Summarize what we accomplished and what's next." Save that output, then paste it back when you restart:

goose
# paste: "We were refactoring the UserProfile component, fixing prop validation..."

3. Project-specific context with .goosehints - Create a .goosehints file in your repo root with standing instructions:

This is a React/TypeScript project using Vite.
Main components are in src/components/.
We're currently refactoring user authentication.

Goose automatically reads this on startup.

[Shiven0504]

Also if you are using MCP servers for state (like a notes tool), that can help maintain context across sessions :)

[BittuChan]

thanks @Shiven0504 for your suggestion! The .goosehints file seems to be working for me. I added project context there and now goose picks up where I left off much faster.

Also started keeping a scratch file with "current task" notes that I reference when restarting.
Thanks!