Control Hermes Runtime-Metadata Footers

The /footer command controls a compact runtime-metadata footer on final Hermes replies. When enabled, it can show operational details such as the active model, context usage, and working directory. This is useful for debugging and cost awareness, but it may be noisy or reveal unnecessary environment details in external-facing conversations.

Official reference: https://hermes-agent.nousresearch.com/docs/reference/slash-commands

Choose the audience first

Enable the footer in operator channels, development sessions, and troubleshooting threads where model routing or context pressure affects decisions. Disable it for client-facing copy, polished public responses, and shared rooms where a filesystem path or model label adds no value.

Use /footer on, /footer off, or /footer status. Treat the setting as presentation metadata only: it does not change the model, compress context, or move the working directory.

Footer policy checklist

Identify whether the channel is operational or audience-facing.
Avoid exposing a working directory that contains personal or project names.
Use the footer when comparing model routing or context growth.
Keep separate telemetry for cost and usage; a model label is not a billing receipt.
Disable the footer before copying a response into public material.
Recheck the state after moving to another session or platform.
Keep sensitive debugging details in private channels.

Read the fields correctly

Context percentage is a pressure signal, not a quality score. The working directory describes the agent's current file scope, not every path it can access. The model label identifies the selected runtime route but may not explain provider fallback, auxiliary tools, or final billing on its own.

Pitfalls

Leaving private path fragments in a customer-visible message.
Interpreting context percentage as percent complete.
Assuming the footer proves which provider billed every auxiliary operation.
Enabling metadata everywhere and making routine replies harder to read.
Copying the footer into documents where it becomes stale.

Verification steps

Run /footer status in the target surface.
Toggle it on and inspect one final reply.
Verify the fields are accurate and appropriate for the audience.
Confirm interim/tool messages do not create misleading final footers.
Toggle it off and verify the next final reply is clean.
Repeat on the actual gateway platform if CLI behavior is not the target.