Skip to content

[功能] openviking #218

@3150214587

Description

@3150214587

功能描述

Function Description
It is hoped that a collapsible external memory plugin (such as openviking) can be added to write back memory information. The messages sent for usage will have the field {supplementary memory} added in front. It is hoped that support for collapsing this field can be provided. Otherwise, it affects the experience.

Usage Scenario
Because every sent message is written back, not collapsing it affects the visual experience.

Possible Implementation Plan
I believe it can be implemented in the following way:

Support configuration of custom message collapse options, folding this type of format to show only a title (which can be customized, for example: openviking appended memory)

Alternative Plan
No response

Additional Information
This is an example of a user message being written back.

使用场景

openvikingFunction Description
It is hoped that a collapsible external memory plugin (such as openviking) can be added to write back memory information. The messages sent for usage will have the field {supplementary memory} added in front. It is hoped that support for collapsing this field can be provided. Otherwise, it affects the experience.

Usage Scenario
Because every sent message is written back, not collapsing it affects the visual experience.

Possible Implementation Plan
I believe it can be implemented in the following way:

Support configuration of custom message collapse options, folding this type of format to show only a title (which can be customized, for example: openviking appended memory)

Alternative Plan
No response

Additional Information
This is an example of a user message being written back.

可能的实现方案

Function Description
It is hoped that a collapsible external memory plugin (such as openviking) can be added to write back memory information. The messages sent for usage will have the field {supplementary memory} added in front. It is hoped that support for collapsing this field can be provided. Otherwise, it affects the experience.

Usage Scenario
Because every sent message is written back, not collapsing it affects the visual experience.

Possible Implementation Plan
I believe it can be implemented in the following way:

Support configuration of custom message collapse options, folding this type of format to show only a title (which can be customized, for example: openviking appended memory)

Alternative Plan
No response

Additional Information
This is an example of a user message being written back.

替代方案

Function Description
It is hoped that a collapsible external memory plugin (such as openviking) can be added to write back memory information. The messages sent for usage will have the field {supplementary memory} added in front. It is hoped that support for collapsing this field can be provided. Otherwise, it affects the experience.

Usage Scenario
Because every sent message is written back, not collapsing it affects the visual experience.

Possible Implementation Plan
I believe it can be implemented in the following way:

Support configuration of custom message collapse options, folding this type of format to show only a title (which can be customized, for example: openviking appended memory)

Alternative Plan
No response

Additional Information
This is an example of a user message being written back.

补充信息

Function Description
It is hoped that a collapsible external memory plugin (such as openviking) can be added to write back memory information. The messages sent for usage will have the field {supplementary memory} added in front. It is hoped that support for collapsing this field can be provided. Otherwise, it affects the experience.

Usage Scenario
Because every sent message is written back, not collapsing it affects the visual experience.

Possible Implementation Plan
I believe it can be implemented in the following way:

Support configuration of custom message collapse options, folding this type of format to show only a title (which can be customized, for example: openviking appended memory)

Alternative Plan
No response

Additional Information
This is an example of a user message being written back.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions