Skip to content

WebUI: Show session timestamps in sidebar + export session as markdown #4579

Description

@3L1AS

Feature Request

Two small WebUI UX improvements that fit nanobot's "keep it tiny" philosophy. Both are minimal code changes, high daily value for power users with multiple parallel sessions.


1. Session timestamps in sidebar

Problem: The sidebar lists sessions but shows no date/time. When you have many sessions (e.g. per client, per project), it's impossible to tell which are recent vs. stale without opening them.

Proposal: Display lastActive timestamp next to each session name in the sidebar. Something like:

📌 Prompt XXL — Growth
   DiGiDENT — SEO
   Noll — Content Batch
─────
   General Q&A          2h ago
   Flight search         yesterday
   Debug cron            3 days ago

Subtle formatting (muted color, relative time like "2h ago") to keep the UI clean. No click interaction needed, just informational.

Effort: Likely a 1-line change per session item in the sidebar component (sessions already have timestamps stored).


2. Export session as markdown

Problem: Sessions live only inside nanobot. No way to share a conversation with a collaborator, save it for reference outside nanobot, or archive it.

Proposal: Add an export button (e.g. download icon on a session) that serializes the session to a .md file:

  • Speaker labels (User / Assistant) per message
  • Timestamps per turn (optional)
  • Tool calls summarized or collapsed
  • Code blocks preserved

Example output:

# Session: Prompt XXL Growth — Jun 28, 2026

## User (15:31)
What's the current status of the outreach pipeline?

## Assistant (15:32)
Here's the summary from `projects/promptxxl/growth/outreach/`:
- 12 directories submitted
- 3 pending verification
...

The exported file gets sent via the active channel (Telegram file, email attachment) or downloaded directly in the WebUI.

Effort: Sessions are already stored in memory/database. This is mostly serialization + a UI button. Maybe 20-30 lines total.


Why these two?

Both solve real daily friction for users running multiple parallel sessions across different projects/clients. Neither requires new infrastructure, new dependencies, or architectural changes. They're additive UI polish on existing data.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions