Skip to main content
Every analysis you perform is automatically saved to your personal history, allowing you to revisit and reference past argument maps.

Accessing Your History

1

Navigate to History

Click on the “History” link in the main navigation menu.
2

View your analyses

You’ll see a grid of cards showing all your saved argument analyses.
3

Browse chronologically

Analyses are sorted by creation date, with the most recent appearing first.
You must be logged in to access your analysis history. If you’re not authenticated, you’ll be redirected to the login page.

History Page Features

The history page displays your analyses in an organized grid layout:

Analysis Cards

Each card shows the analysis name and creation timestamp

Chronological Sorting

Most recent analyses appear first

Responsive Grid

Layout adapts: 1 column (mobile), 2 columns (tablet), 3 columns (desktop)

Quick Metadata

See when each analysis was created (e.g., “2 hours ago”, “3 days ago”)

Analysis Card Information

Each history card displays:
  • Analysis Name: The topic, URL, or first 150 characters of your input
  • Creation Date: Relative timestamp (e.g., “2 hours ago”, “3 days ago”)
  • Visual Feedback: Cards show hover effects for better interactivity
The analysis name is automatically generated:
  • For Topic inputs: First 150 characters of your query
  • For URL inputs: The complete URL
  • For Document inputs: First 150 characters of the text

How History is Stored

Firestore Data Structure

Your analyses are stored in a Cloud Firestore database with the following structure:
users/
  └── {userId}/
      └── argumentMaps/
          ├── {documentId1}/
          │   ├── id: string
          │   ├── userId: string
          │   ├── name: string
          │   ├── creationDate: timestamp
          │   └── jsonData: string
          ├── {documentId2}/
          └── {documentId3}/

Document Fields

Each saved analysis contains:

Document ID

Type: stringAuto-generated unique identifier for the analysis.
id: "abc123def456"
This ID is used to retrieve specific analyses and matches the Firestore document ID.

Automatic Saving

Every successful analysis is automatically saved:
1

Analysis completes

After the AI generates your argument blueprint successfully.
2

Document created

A new document is created in your Firestore collection.
3

Data stored

All analysis results are serialized and saved.
4

Timestamp recorded

Server timestamp is automatically added.
Saving happens in the background. Even if saving fails, you’ll still see your analysis results—you just won’t be able to access them later from history.

Data Persistence

How Long is Data Stored?

Your analysis history is stored indefinitely unless you manually delete items or close your account.
Key points about data persistence:
  • No automatic deletion: Analyses remain until you remove them
  • User-scoped: Only you can access your analyses
  • Server-side timestamps: Creation dates are reliable and timezone-independent
  • Full fidelity: Complete analysis data is preserved, including all nodes and metadata

Privacy & Security

Private by Default

Analyses are stored under your user ID—no one else can access them

Authenticated Access

Firebase security rules ensure only authenticated owners can read their data

Server-side Validation

Authentication tokens are verified before saving or retrieving analyses

Encrypted Transport

All data transmission uses HTTPS encryption

Loading States

The history page handles various states gracefully:

Loading State

While fetching your history from Firestore:
  • A loading spinner is displayed
  • The page shows “Loading…” feedback
  • Navigation remains accessible
This typically takes 1-2 seconds on first load.

Querying Your History

Behind the scenes, the history page uses an optimized Firestore query:
query(
  collection(firestore, 'users', userId, 'argumentMaps'),
  orderBy('creationDate', 'desc')
)
This query:
  • Fetches all documents in your argumentMaps subcollection
  • Sorts by creationDate in descending order (newest first)
  • Uses Firestore indexes for fast retrieval
  • Automatically syncs with real-time updates

Limitations & Notes

Currently, the history page displays analysis metadata but doesn’t yet allow you to view the full analysis results.The “View Analysis” button is disabled with a “(Soon)” label. This feature is planned for a future update.Workaround: Re-run the same analysis to generate fresh results.
The current version doesn’t include search or filtering capabilities.All analyses are displayed chronologically. To find a specific analysis, scroll through the list.Tip: Use descriptive topics when creating analyses to make them easier to identify later.
There’s currently no way to delete individual analyses from the history page.This feature may be added in future updates.
While you can export analysis results immediately after generation, you cannot currently export from the history page.See the Exporting Data guide for current export options.

Best Practices

Descriptive Queries

Use clear, descriptive topics so you can identify analyses later

Regular Reviews

Periodically review your history to revisit insights

Stay Logged In

Keep your authentication session active to access history

Note-Taking

Consider taking external notes for important findings

Troubleshooting

If you’re redirected to the login page when accessing history:
  • Your authentication session may have expired
  • You may not be logged in
  • There may be a problem with your auth token
Solution: Log in again to restore access to your history.
If the loading spinner persists:
  • Check your internet connection
  • Verify Firebase services are operational
  • Try refreshing the page
  • Clear browser cache and try again
Solution: Wait a moment and refresh, or check the browser console for error details.
If a recent analysis doesn’t appear:
  • The save operation may have failed silently
  • Check the browser console for Firestore errors
  • Verify your authentication was valid during analysis
Solution: Re-run the analysis. If the problem persists, check Firebase configuration.
If you see an error message:
  • Firestore security rules may be misconfigured
  • Your user account may have permission issues
  • The database may be temporarily unavailable
Solution: Contact support or check Firebase console for issues.

Future Enhancements

Planned features for history management:
  • View full analysis from history
  • Search and filter capabilities
  • Delete individual analyses
  • Rename analyses
  • Export multiple analyses at once
  • Share analyses with others
  • Tag and categorize analyses
  • Comparison view for multiple analyses

Build docs developers (and LLMs) love