change identity PicoClaw

[Fieter955]

i tried so many times to change the soul.md, identity.md etc. i am using docker, i already remove all my configuration and directory and rebuild docker. i make sure to change first the soul.md etc before docker compose, i also remove the volume in my docker. but when i try ask again in telegram the name still PicoClaw

anybody can help me?

[Fieter955]

when i start the name still same, but it turns out when i try to chat it works.

[tomas2387]

That's because the greetings message is hardcoded.
It will always be "Hello! I am PicoClaw" to be fast and to not depend on any external service.

picoclaw/pkg/channels/telegram_commands.go

Line 57 in 8d757fb

Text: "Hello! I am PicoClaw 🦞",

The next messages are connected to the LLM, and therefore read the soul.md.

Does this answer your issue?

[nikolasdehor]

@tomas2387 is right — the greeting is hardcoded in pkg/channels/telegram_commands.go:57:

"Hello! I am PicoClaw, ..."

There is an open PR that fixes this: PR #303 — makes the greeting name configurable via a bot_name field in agents.defaults config. With that PR, the config would look like:

{
  "agents": {
    "defaults": {
      "bot_name": "MyAssistant"
    }
  }
}

And all channel greetings (Telegram /start, DingTalk, etc.) would use the configured name instead of the hardcoded "PicoClaw".

For Docker users specifically: Until PR #303 is merged, the workaround is to mount a patched binary or rebuild the image with the greeting string changed. But since soul.md works for all subsequent messages (as @Fieter955 confirmed), the greeting is really the only place where the hardcoded name leaks through.

Worth noting that the AIEOS proposal (#296, PR #469) would also solve this more comprehensively by deriving the agent's name from a structured identity profile. But PR #303 is the simpler, immediate fix.

[Fieter955]

That's because the greetings message is hardcoded. It will always be "Hello! I am PicoClaw" to be fast and to not depend on any external service.

picoclaw/pkg/channels/telegram_commands.go

Line 57 in 8d757fb

Text: "Hello! I am PicoClaw 🦞",
The next messages are connected to the LLM, and therefore read the soul.md.

Does this answer your issue?

wooww thankss

[Fieter955]

@tomas2387 is right — the greeting is hardcoded in pkg/channels/telegram_commands.go:57:

"Hello! I am PicoClaw, ..."
There is an open PR that fixes this: PR #303 — makes the greeting name configurable via a bot_name field in agents.defaults config. With that PR, the config would look like:

{
"agents": {
"defaults": {
"bot_name": "MyAssistant"
}
}
}
And all channel greetings (Telegram /start, DingTalk, etc.) would use the configured name instead of the hardcoded "PicoClaw".

For Docker users specifically: Until PR #303 is merged, the workaround is to mount a patched binary or rebuild the image with the greeting string changed. But since soul.md works for all subsequent messages (as @Fieter955 confirmed), the greeting is really the only place where the hardcoded name leaks through.

Worth noting that the AIEOS proposal (#296, PR #469) would also solve this more comprehensively by deriving the agent's name from a structured identity profile. But PR #303 is the simpler, immediate fix.

thanks for the responsed. it is help me understand deepeer