nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Should --restore be the default?

Uwe Strepp

For me it's the default use-case, when starting the agent in a specific project. So rather then having to actively --restore the session, why not have (e.g.) a --clear flag to optionally start fresh when necessary or convenient?

Comments

rmoriz

I'm not sure if this was implemented or I manually changed the config. But it's already possible to do so with:

file: ~/.rovodev/config.yml

…

sessions:
  # Automatically restore the last active session on startup
  autoRestore: true
  # Directory where session data is stored
  persistenceDir: /Users/username/.rovodev/sessions

…

However, keep in mind that a session creates context, context can growth fast and is usually not helping to improve the LLM results. Hence, when you start a new task, it's better to call /prune or even start a new session.

Jovana Dunisijevic

Hey @Uwe Strepp

Thanks for your suggestion!

Having a --clear flag to start a fresh session by default (instead of always restoring the previous one) makes a lot of sense, especially for users who frequently switch projects or want a clean slate. I'll share this feedback with the product team for consideration in future updates.

In the meantime, please continue to use --restore as needed or take @rmoriz recommendation which is also a very good practice we do internally!

Kindest regards,

Jov

Welcome!

It looks like you're new here. Sign in or register to get started.