[PR #12] [MERGED] Ability to set auto-generate tasks frequency. #15

New issue

Closed

opened 2026-10-15 13:26:32 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 13:26:32 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/SillyTavern/Extension-Objective/pull/12
Author: @Satoshi-Yoda
Created: 3/30/2025
Status: ✅ Merged
Merged: 4/1/2025
Merged by: @Cohee1207

Base: main ← Head: main

📝 Commits (2)

d67382f Added ability to set auto-generate tasks frequency.
35e95b2 css addition

📊 Changes

3 files changed (+39 additions, -5 deletions)

View changed files

📝 index.js (+26 -4)
📝 settings.html (+8 -1)
📝 style.css (+5 -0)

📄 Description

Hi! ^_^
Here is why and here is how.

Why:

First. Because without it the dialog could easily fall into a trapped state.
For example, let's say there is a subtask Make the {{user}} take an umbrella.
And there is an actual dialog:

> AI: "Hey, those clouds look shifty — maybe grab an umbrella?"
> User: "Nah, let the sky try me."

And that's it. Bad.
Next it will follow one of those paths (depending on the context, model, and Position in Chat value):

Stuck: will never mention it in dialog, will never mark it as done.
Overzealous: will repeatedly try something "Take an umbrella with you. Seriously, take it. You must take it. I still insist you take it."
Confused: if for some reason task will be marked as done (after a dozen of AI checks due to some random noise), and the next task relies on the presence of such umbrella, it could materialize it out of a thin air or lead to some logic gibberish.

Second. Because dialog could naturally flow to some another context, where the generated tasks are no longer relevant. For example, they were generated in some strictly indoor context, and the dialog moved outdoor.

Third. It is helpful for creating moving (shifting / following) tasks without strict end goal. Something like "generate some challenges for the {{user}} given the current state".

How:

Here, I am not sure I understood correctly the part with "Don't let counter go negative".
I removed the comment (sorry about that =), and moved counter re-initialization from the separate function right in place.
And did the same for the new counter. Seems to work with zero and non-zero case, but maybe I missed something?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/SillyTavern/Extension-Objective/pull/12 **Author:** [@Satoshi-Yoda](https://github.com/Satoshi-Yoda) **Created:** 3/30/2025 **Status:** ✅ Merged **Merged:** 4/1/2025 **Merged by:** [@Cohee1207](https://github.com/Cohee1207) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`d67382f`](https://github.com/SillyTavern/Extension-Objective/commit/d67382f5d84aa8d88398f9a453b0942109a1650c) Added ability to set auto-generate tasks frequency. - [`35e95b2`](https://github.com/SillyTavern/Extension-Objective/commit/35e95b2f5261af772a28acb7217d388df8bbfe79) css addition ### 📊 Changes **3 files changed** (+39 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `index.js` (+26 -4) 📝 `settings.html` (+8 -1) 📝 `style.css` (+5 -0) </details> ### 📄 Description Hi! ^_^ Here is why and here is how. ### Why: First. Because without it the dialog could easily fall into a trapped state. For example, let's say there is a subtask `Make the {{user}} take an umbrella.` And there is an actual dialog: ``` > AI: "Hey, those clouds look shifty — maybe grab an umbrella?" > User: "Nah, let the sky try me." ``` And that's it. Bad. Next it will follow one of those paths (depending on the context, model, and Position in Chat value): - Stuck: will never mention it in dialog, will never mark it as done. - Overzealous: will repeatedly try something "Take an umbrella with you. Seriously, take it. You must take it. I still insist you take it." - Confused: if for some reason task will be marked as done (after a dozen of AI checks due to some random noise), and the next task relies on the presence of such umbrella, it could materialize it out of a thin air or lead to some logic gibberish. Second. Because dialog could naturally flow to some another context, where the generated tasks are no longer relevant. For example, they were generated in some strictly indoor context, and the dialog moved outdoor. Third. It is helpful for creating moving (shifting / following) tasks without strict end goal. Something like "generate some challenges for the {{user}} given the current state". ### How: Here, I am not sure I understood correctly the part with "Don't let counter go negative". I removed the comment (sorry about that =), and moved counter re-initialization from the separate function right in place. And did the same for the new counter. Seems to work with zero and non-zero case, but maybe I missed something? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 13:26:32 +00:00

closed this issue
added the
pull-request
label

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

SillyTavern/Extension-Objective#15

No description provided.

Rows
Columns