#Personality is stuck to kawaii

1 messages · Page 1 of 1 (latest)

junior cypress
#

Hi i tried to change personality,it wont change whatsoever
I did restart didnt fix
https://paste.rs/jd3iD
Can anyone suggest me a solution

weary geode
#

The paste does not show a confirmed personality command failure yet.

In Hermes, /personality none or /personality default clears the personality overlay, but it does not erase the existing Telegram conversation history. A gateway restart also does not necessarily remove the active session transcript.

In your log, one Telegram group message starts with:

You are baymex Job Agent...

If that was in the same chat/session, the model can keep following that as conversation context even after you change the personality.

Try this in the exact Telegram chat where it is stuck:

/personality none
/reset

Then send a plain test message like:

Reply in a neutral tone, no kawaii style.

Also check whether you have a custom base identity in:

~/.hermes/SOUL.md

/personality none clears the config personality overlay, but it does not erase SOUL.md. If SOUL.md contains kawaii/personality text, edit that file too.

If it still acts kawaii after /personality none plus /reset, please paste:

grep -n "system_prompt\|personality" ~/.hermes/config.yaml
sed -n '1,80p' ~/.hermes/SOUL.md

and a fresh /debug from the same Telegram chat after reproducing it.

onyx kiln
weary geode
#

could be. your logs dont show anything but a couple of hi's. you prob just need to start a new session so that the system prompt is rebuilt

#

like, i dont seee any attempt at changing personality at all in there.

#

could also be memories

#

i'm not sure what you're seeing. it's not in the logs at all.

junior cypress
weary geode
#

all good. if you can fill me in on what you're seeing i can possibly help, but rn i don't have anything to go on. have you tried the suggestions?

#

model: qwen/qwen3-next-80b-a3b-instruct
provider: nvidia
this model might also just be kinda that way? idk

#

Were you able to resolve this or can you reproduce it and provide the new logs from /debug?

junior cypress
#

No i just reinstalled it and its working fine now

#

But again ine thing cant select surfer

weary geode
#

I'm not sure what the thing is or the surfer. Can you describe the issue?

junior cypress
#

Its a personality

#

Shows in list

weary geode
#

surfer is a built-in personality, so if it shows in /personality but will not select, I need the exact failure output.

In the same Telegram chat where it fails, please run:

/personality surfer

Then paste the exact reply Hermes gives you.

After that, run:

/debug

and send the debug links here.

Also tell me whether this is Telegram DM, group, or topic/thread. The earlier logs did not show the failed personality command, so I need a fresh repro from the chat where it is actually happening.

junior cypress
#

Okay done brb

weary geode
#

First: delete that paste and rotate your Telegram bot token.

The debug log includes a Telegram bot token in the conversation text. Treat that token as compromised now:

  1. Delete the paste.
  2. Open BotFather.
  3. Revoke/regenerate the bot token.
  4. Update Hermes with the new token.

For the personality issue: the logs show Hermes is receiving and sending messages in that Telegram group topic, and there is a short command response right before your next test message. That looks like /personality surfer probably did run, but the topic already has a long existing session/context, so the old behavior can keep bleeding through.

In the exact Telegram topic where this is stuck, run:

/personality surfer

Confirm Hermes replies with:

Personality set to surfer

Then run:

/reset

Then test with:

Say one sentence in your current personality.

If it is still not using surfer after that, send a new /debug from that same topic after rotating the bot token. The new debug needs to include the /personality surfer, /reset, and test message sequence.

#

in fact, i'll delete if for you from here.

#

and update before you send another debug log because there are fixes for this token redaction upstream from your build

#

The token was in the output because the user pasted the Telegram bot token into the Telegram chat. I would not put any creds into any chat. treat these as secrets.