u/alvinunreal

For developers, pets can be integrated with coding agents, or can be used to trigger reactions via CLI.

Repo link: https://github.com/alvinunreal/openpets

https://openpets.dev/

Hey guys, wanted to give quick update regarding the claude-pets projects i shared recently.

I merged it with openpets.dev - and started generating original pets.
With this merge, onboarding is much easier and simpler integration also much more improved.

Besides, I started publishing original pets, and first batch is out. Will add more.!

Repo: https://github.com/alvinunreal/openpets

New /subtask feature in omo-slim. Use it to keep the main Orchestrator context lean.

subtask spawns a separate Orchestrator agent to accomplish the given task and returns summary.

Orchestrator can also auto-use /subtask when it's relevant.

Repo: https://github.com/alvinunreal/oh-my-opencode-slim

merged it to https://openpets.dev/

It started all with Claude Pets posts: https://www.reddit.com/r/ClaudeAI/comments/1t48531

so here is the new, improved version of it.

New version has easier, simpler onboarding and per project pet support.
Besides added ability to import Codex pets, and published Opencode integration too.

Repo link: https://github.com/alvinunreal/openpets
Website: https://openpets.dev/

tmuxai.dev

I built Claude version of pets.
Here is the repo if you want to try: https://github.com/alvinunreal/claude-pets

You can find more pets over here: https://openpets.dev

*EDIT
Thank everyone for positive response.
Right now it's only possible to launch a single pet, I will be adding ability to launch many pets and tie any pet to any project/session. This should make working with multiple claude sessions easier

Track subreddit growth, related subreddits, or group by topics - no sign up required.

I built https://freesubstats.com/ a while back and updated it recently.

I liked the idea, and purchased also Divoom Minitoo and here is the video how I integrated with omo-slim.

Have to say, opus really struggled, wasted few hours and GPT solved quite quickly; I used rooted android device to decode bluetooth traffic;

Got what I was looking for. Here is the protocol code itself if anyone wants to play around: https://github.com/alvinunreal/divoom-minitoo-osx

If OpenClaw config changes, repo checks, cron issues, and bot maintenance all happen in the same general chat, operational work gets mixed into everything else. A dedicated Telegram topic with its own systemPrompt gives OpenClaw a standing admin lane for config review, source inspection, and safe git follow-up.

This works well for things like checking repo status, reviewing changed files, suggesting .gitignore updates, or preparing commits for your OpenClaw config workspace without dragging product or client chatter into the same thread.

Use a topic-specific prompt under the exact Telegram account and chat path you already use. For account-nested Telegram config, it can look like this:

{
  channels: {
    telegram: {
      max: {
        enabled: true,
        direct: {
          "*": {
            topics: {
              "1398645": {
                systemPrompt: "This is the OpenClaw admin topic. In this topic, manage my OpenClaw config, inspect OpenClaw source when needed, review repo status, suggest what should be committed or ignored, and ask before making git commits. OpenClaw source code is in ~/.openclaw/ and my global config is in ~/.openclaw/openclaw.json. I do clean, git management of openclaw directory, trying to ingore not for source code useful stuff, and include everything for reproducable re-setup. Usually after making changes, I commit my config dir, for this you can report to me changed files, what's good to commit and what's to ignore, if igoring should we add in .gitinore too and if I approve, you can commit"
              }
            }
          }
        }
      }
    }
  }
}

Keep the prompt narrow and operational. Tell the topic what it is for, where the OpenClaw repo lives, where the active config lives, and what commit behavior you want. If you want approval before commits or `.gitignore` changes, say that directly in the topic prompt.

This is different from a generic project topic. The point is to have one permanent thread that OpenClaw treats as its own maintenance console.

Review my OpenClaw Telegram setup and create a dedicated Telegram topic for OpenClaw admin work so I can manage config and repo changes quickly without mixing that work into other chats.

Do all of the following:

1. Find the active OpenClaw config file actually used by this runtime.
2. Check which Telegram account and chat path this conversation uses.
3. Identify the exact topic/thread id I want to dedicate to OpenClaw admin work.
4. Add or update a topic-specific `systemPrompt` at the correct Telegram config path for that topic.
5. Keep unrelated Telegram settings intact.
6. Make the prompt explicitly cover:
   - OpenClaw config review
   - OpenClaw source inspection when needed
   - repo status checks
   - recommendations for what to commit vs ignore
   - asking for approval before commits or `.gitignore` changes unless I said otherwise
7. Include the real important paths in the prompt, such as my OpenClaw repo path and active config path.
8. If this setup is account-nested, apply the change under the correct account entry instead of the shared default path.
9. Test the topic if possible by asking for repo status or config status inside that topic.
10. Do not claim success unless the topic is configured and the behavior reflects the topic-specific prompt.

<systemPrompt>
This is the OpenClaw admin topic. In this topic, manage my OpenClaw config, inspect OpenClaw source when needed, review repo status, suggest what should be committed or ignored, and ask before making git commits. OpenClaw source code is in ~/.openclaw/ and my global config is in ~/.openclaw/openclaw.json. I do clean, git management of openclaw directory, trying to ingore not for source code useful stuff, and include everything for reproducable re-setup. Usually after making changes, I commit my config dir, for this you can report to me changed files, what's good to commit and what's to ignore, if igoring should we add in .gitinore too and if I approve, you can commit
</systemPrompt>

Then show me:
- which config file you changed
- the exact Telegram topic config block before and after
- which Telegram account, chat id, and topic/thread id were configured
- the exact `systemPrompt` now used for that topic
- whether you tested it in that topic
- any assumptions you made

One long OpenClaw conversation turns into a junk drawer. Coding, research, admin, and random questions all get mixed together, and every new turn drags that baggage forward.

OpenClaw already has session boundaries you can use. Group chats isolate state by group. Telegram forum topics get their own :topic:<threadId> session keys. Slack and Discord threads are treated as thread sessions. Discord channels also get their own isolated sessions.

That means the practical fix is simple: split work by topic or channel. Keep one thread for coding, another for research, another for admin, another for personal operations. Focused threads give the agent focused context instead of one huge mixed transcript.

This is one of the easiest memory fixes because it does not require a new memory system. It just uses OpenClaw's existing session isolation properly.

For Telegram specifically, BotFather has a setting for this now. Open BotFather, choose your bot from My bots, go to Bot Settings, and turn on Threaded Mode.

Once it is enabled, Telegram gives the bot separate tabs/topics in the chat UI. That is exactly what this tip needs - coding in one topic, research in another, admin in another - instead of one mixed transcript where everything contaminates everything else.