agentscope-ai / agentscope-ai/agentscope-java

[Feature]: Agui mode does not expose sessionId during agent execution, preventing saveTo / session persistence

Offen
#751 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area/ext/integration enhancement
Vorherrschende Sprache
Java
Sterne
5.6k
Forks
1.3k
Ø Merge
4 T. 12 Std.
Gemergte PRs (30 T.)
77

Beschreibung

## Title

Agui mode does not expose sessionId during agent execution, preventing saveTo / session persistence

## Is your feature request related to a problem? Please describe.

In Agui mode, we need to persist agent conversation state (e.g. messages / memory) using the existing AgentScope session mechanism.

However, during the agent execution lifecycle in Agui, there is currently no way to obtain the `sessionId` (or `SessionKey` / `threadId`) required for `agent.saveTo(...)` or other session persistence operations.

Although it is possible to access the `Agent` instance from certain hooks, the lack of session context makes it impossible to correctly save or restore conversation history.

This prevents message persistence and session-based state recovery when running agents through Agui.

## Describe the solution you'd like

We would like Agui to expose or propagate the session context during agent execution, for example:

- Provide access to `sessionId` / `threadId` / `SessionKey` in Agui hooks
- Or offer an official extension point in Agui to perform session persistence (e.g. `saveTo`)
- Or pass session-related metadata together with the `Agent` instance during execution

This would allow Agui-based executions to integrate cleanly with AgentScope’s existing Session / Memory persistence mechanisms.

## Describe alternatives you've considered

- Triggering `saveTo` manually inside hooks using the `Agent` instance
→ Not feasible because `sessionId` is not available

- Managing a separate persistence mechanism outside of AgentScope
→ Causes duplication and breaks consistency with the existing Session design

## Additional context

Currently, message saving and loading works correctly when using AgentScope directly, but not when running agents through Agui.

Supporting session persistence in Agui would enable:
- Multi-turn conversation continuity
- Proper memory loading and saving
- Better alignment between Agui and AgentScope core session behavior

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.