How to assign a cron job to a specific model?

[fablau]

How can I ensure that a specific cron job always uses a specific model instead of the default one? Is there any way to do that? From the documentation, I don't currently see a way to directly assign a specific model to a specific cron job, but maybe there is a workaround?

[chengyongru]

Currently, there is no way to assign a specific model to a particular cron task.

[fablau]

Thank you for replying... can you think of any workaround? For example, a cron job that calls a script to switch the model or tell the model to switch to another model?

[chengyongru]

Let me look into how to directly support your needs; this feature is quite necessary.

[chengyongru]

The current cron task is bound to the session, and the model of each session can be freely switched without affecting each other.

[fablau]

Thank you! Is this a new feature of the latest 0.3 version?

[chengyongru]

yes

[fablau]

I am not sure how to use it for cron jobs. For example, if I want only a specific cron job to use a specific model but have all other cron jobs and chat use a different one, how can I do that?

[chengyongru]

You can do this by using a separate topic/session for that cron job:

1. Create a dedicated topic/session for the job.
2. In that topic, switch to the desired model preset, for example:

/model deep

3. Create the cron job from that same topic.

The cron job is bound to the session where it was created, and it inherits that session’s model preset. Other topics/sessions can use a different preset without affecting it.

However, multiple cron jobs created in the same session share that session’s model selection. So if two cron jobs need different models, create them in two separate topics/sessions and select the corresponding preset in each one.

The preset itself is configured in modelPresets in config.json, while /model <preset> only changes the current session and does not change the global default.

There is currently no per-job model parameter in the cron tool; the session/topic is the isolation boundary for model selection.

[fablau]

That's brilliant! So, can a Telegram group be considered a "topic"? I am using Telegram for most of my work with Nanobot.

[chengyongru]

yes

[chengyongru]

You can easily conduct an experiment by switching presets with /model in different groups, and you will find that they do not affect each other.

[fablau]

Thank you!