Hermes Agent's/backgroundis suitable for running long tasks in independent sessions, such as server inspection, data research, and batch organization of files. It won't jam your current chat and will return to the same chat or channel when it's completed.How to use_CODE_BLOCK_0___ HTML_4 After sending it, Hermes will immediately return that the background task has been started. This backend agent inherits the current gateway's model, provider, toolsets, and routing configuration, but it has its own independent context.
The most misunderstood point
- Multiple background tasks can be run at the same time, but avoid having them change the same batch of files at the same time.
- When the result fails, the reason for the failure will be returned. Don't just look at whether there is a final summary. In a word: - /background means "opening a separate agent to do things", not temporarily suspending the current conversation. suitable for writing background tasks prompt
When writing_CODE_INLINE_2__, you should explain clearly the goal, scope, and output format at one time. For example,"Check the 5xx in the last 2 hours in/var/log/nginx/error.log, sort it by the number of occurrences, and only give the 3 questions that need to be dealt with." Don't just write "Help me check the server". The background conversation does not have all the context in your current chat. Writing too much will increase misjudgment. If the task requires you to confirm it halfway, do not put it in the background; if the task only requires the final result, it is very suitable for putting it in the background. Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
