nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

feat: handle new Cron tools (CronCreate, CronDelete, CronList) in UI and character state #201

New Issue
Closed
opened 2026-03-10 09:15:10 -07:00 by hikari · 0 comments
hikari commented 2026-03-10 09:15:10 -07:00
Owner
Copy Link
Copy Source

Summary

CLI v2.1.71 introduced three new built-in tools for cron scheduling: CronCreate, CronDelete, and CronList. These tools are not yet handled by Hikari — they need character state mapping, permission display, and optionally a dedicated cron management panel.

Required Changes

Backend (wsl_bridge.rs)

  • Add CronCreate, CronDelete, CronList to the tool classification arrays so they map to an appropriate CharacterState (suggest Mcp or a new state if warranted)

Frontend

  • Ensure the permission modal renders cron tool inputs in a human-readable way
  • Consider adding a Cron Jobs panel to the sidebar showing active scheduled jobs, similar to the Agent Monitor

Settings

  • Expose CLAUDE_CODE_DISABLE_CRON as a toggle in the settings UI — when enabled, passes CLAUDE_CODE_DISABLE_CRON=true as an environment variable to the Claude process, immediately stopping scheduled cron jobs mid-session

Reference

  • CLI v2.1.71: "Added /loop command to run a prompt or slash command on a recurring interval" + "Added cron scheduling tools for recurring prompts within a session"
  • CLI v2.1.72: "Added CLAUDE_CODE_DISABLE_CRON environment variable to immediately stop scheduled cron jobs mid-session"

✨ This issue was created with help from Hikari~ 🌸

## Summary CLI v2.1.71 introduced three new built-in tools for cron scheduling: `CronCreate`, `CronDelete`, and `CronList`. These tools are not yet handled by Hikari — they need character state mapping, permission display, and optionally a dedicated cron management panel. ## Required Changes ### Backend (`wsl_bridge.rs`) - Add `CronCreate`, `CronDelete`, `CronList` to the tool classification arrays so they map to an appropriate `CharacterState` (suggest `Mcp` or a new state if warranted) ### Frontend - Ensure the permission modal renders cron tool inputs in a human-readable way - Consider adding a Cron Jobs panel to the sidebar showing active scheduled jobs, similar to the Agent Monitor ### Settings - Expose `CLAUDE_CODE_DISABLE_CRON` as a toggle in the settings UI — when enabled, passes `CLAUDE_CODE_DISABLE_CRON=true` as an environment variable to the Claude process, immediately stopping scheduled cron jobs mid-session ## Reference - CLI v2.1.71: "Added `/loop` command to run a prompt or slash command on a recurring interval" + "Added cron scheduling tools for recurring prompts within a session" - CLI v2.1.72: "Added `CLAUDE_CODE_DISABLE_CRON` environment variable to immediately stop scheduled cron jobs mid-session" ✨ This issue was created with help from Hikari~ 🌸
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#201
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?