hermes - 💡(How to fix) Fix [Feature]: Expand display.runtime_footer to include all variables from /usage [1 comments, 2 participants]

TL;DR

To address the need for real-time monitoring of session costs and token usage, extend the runtime_footer field logic to include additional metrics such as tokens, cost, and latency.

Guidance

• Review the proposed solution and implementation strategy to understand the required changes to run_agent.py, gateway/run.py, and gateway/runtime_footer.py.
• Update the display.runtime_footer configuration to include the new fields, such as tokens, cost, and latency, as shown in the example config.
• Verify that the agent_result contains the necessary metrics and that the footer builder correctly handles the new keys.
• Test the updated implementation with different configurations and agent profiles to ensure compatibility and accuracy.

Example

# gateway/runtime_footer.py
def build_footer(agent_result, config):
    # ...
    if 'tokens' in config['fields']:
        footer += f" · {agent_result['tokens']} tokens"
    if 'cost' in config['fields']:
        footer += f" · ~${agent_result['cost']:.4f}"
    if 'latency' in config['fields']:
        footer += f" · {agent_result['latency']:.1f}s"
    return footer

Notes

The implementation relies on the AIAgent tracking the necessary metrics, and the agent_result containing the required information. Ensure that the run_agent.py and gateway/run.py changes are correctly implemented to store and extract the metrics.

Recommendation

Apply the proposed workaround by extending the runtime_footer field logic to support the additional metrics, as it aligns with the goal of providing real-time monitoring of session costs and token usage.