PARE Apps Overview

Use this section to understand what actions are available inside the benchmark. Each app page lists the user-facing @user_tool methods, the backend calls they wrap, return values, and navigation effects.

How To Use This In Practice

Most users come here for one of three reasons:

1. To see what a benchmark scenario can do inside a given app.
2. To filter scenarios by app usage before running experiments.
3. To choose which apps are allowed when generating new scenarios.

Find scenarios that use a given app

uv run pare scenarios list --apps StatefulEmailApp

Restrict scenario generation to a set of apps

uv run pare scenarios generate --apps StatefulEmailApp --apps StatefulCalendarApp

• Need to create another app surface? Follow the Adding a Stateful App guide.

• Stateful Contacts App

• Stateful Messaging App
• Stateful Email App
• Stateful Calendar App
• Stateful Cab App
• Stateful Apartment App
• Stateful Reminder App
• Stateful Shopping App
• Stateful Note App

Navigation Framework Recap

• Every stateful app inherits from pare.apps.core.StatefulApp, which binds a navigation state (AppState) before surfacing its tools.
• AppState.get_available_actions() inspects the bound instance for @user_tools so only the active screen's tools appear.
• go_back() is automatically available when the navigation stack contains history and removes the topmost state while returning a short confirmation string.