History
Roster automatically saves every HTTP request you send to history, allowing you to review and replay past requests.
What is History?
History captures complete request and response data for every request sent:
- Request method, URL, headers, body
- Response status, headers, body, timing
- Timestamp of when request was sent
- Environment used (if applicable)
History persists across sessions and survives application restarts.
Viewing History
Access History Panel
History appears in the bottom panel of the main window.
History Entries
Each entry shows:
- Request method and URL
- Response status code
- Timestamp (relative or absolute)
- Response time
Entries are sorted by timestamp (most recent first).
Open from History
Click any history entry to open it in a new tab with:
- Complete request details
- Full response
- All headers
This creates a new editable request tab - you can modify and resend.
Replaying Requests
To replay a request from history:
- Click the history entry
- Request opens in new tab with original configuration
- Click "Send" to execute again
The replayed request:
- Uses current environment variables (not original values)
- Can be modified before sending
- Creates a new history entry when sent
Using History
Compare Responses
Open multiple history entries in tabs to compare responses across time or different environments.
Debug Issues
Review past requests to:
- See what was actually sent
- Check response timing trends
- Verify header values
- Examine error responses
Create New Requests
Use history entries as templates:
- Open history entry
- Modify URL, headers, or body
- Save as new request
History Storage
Native:
~/.local/share/cz.bugsy.roster/session.json
Flatpak:
~/.var/app/cz.bugsy.roster/data/cz.bugsy.roster/session.json
History is stored in JSON format with full request/response data.
Clearing History
Currently, history can be cleared by deleting the session.json file:
# Native
rm ~/.local/share/cz.bugsy.roster/session.json
# Flatpak
rm ~/.var/app/cz.bugsy.roster/data/cz.bugsy.roster/session.json
Then restart Roster.
Privacy Note
History contains complete request and response data, including:
- URLs and query parameters
- Request/response headers
- Request/response bodies
If requests contain sensitive data:
- Use Sensitive-Variables for credentials
- Be aware history file contains plaintext data
- Clear history periodically if needed
Limitations
- History is stored locally only (no cloud sync)
- No built-in UI to clear history (must delete file manually)
- No search/filter functionality (planned for future releases)
- No export functionality for history entries
Next Steps
- Getting-Started - Learn to send requests
- Export - Export requests to other tools