Skip to content

History and projects

History is the audit trail for a noxen session. It records captured intents even when they are auto-forwarded by filters or observed while interception is off.

You can open a project without attaching to an app. This is useful when you only want to review a previous session, inspect captured component communication, or export data.

Each row represents one captured event and includes the hooked class/method, intent fields, outcome, and optional stack trace.

Common outcomes:

OutcomeMeaning
forwardedDelivered unchanged
modified_forwardedModified and then delivered
droppedBlocked
empty/pendingNo final decision was recorded

Type in the search field to filter visible rows in real time. The search matches against class, method, action, component, data, flags, categories, and extra keys and values.

Click any column header to sort by that column. Click again to reverse the order. The default sort is newest first by ID.

Use the button to show or hide individual columns. The selection is stored in the project file and restored on next launch.

The same dialog also lets you set optional widths for Time and long text columns: Method, Class, Component, and Action. Widths can be set from 5 to 150 cells. Empty width fields use Textual’s automatic sizing. Configured widths are stored in the project file.

When an intent is changed before forwarding, History stores both views:

  • the final values that were delivered;
  • the original values captured before modification.

This lets you review what changed without losing the original evidence.

noxen stores session data and UI state in a .noxen project file (SQLite).

Create a new project:

Terminal window
noxen --new-project session

Open an existing project:

Terminal window
noxen --project session.noxen

If no project option is used, a temporary project is created for the running session.

Project files include:

  • captured intents;
  • final outcome;
  • modified and original intent values;
  • Intercept filters.
  • History filters.
  • History column visibility and width preferences.

Use the History clear action when you want to remove the current session rows.

This clears both the in-memory history and the stored intent rows in the current project.

Use the export action to write History entries to JSON. You can export the full history or only the currently filtered History view.

The export is JSON and is suitable for later review, reporting, or external analysis.