agentscope-ai / agentscope-ai/agentscope-java

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

Aperta
#751 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub
area/ext/integration enhancement
Lingua principale
Java
Stelle
5.6k
Fork
1.3k
Merge medio
4g 12h
PR unite (30g)
77

Descrizione

## 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

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.