Automation editor with graphical schedule and assistant; movable chat list groups
Automations
- Job files hold only the instructions; name, schedule, mode, model, approval
mode and time limit are settings in the database (jobs.settings). Existing
files are adopted on start-up (frontmatter into the database and removed from
the file); plain Markdown files registered later get default settings and stay
switched off until scheduled.
- New automation: name, project and a starting point (blank example structure or
a template) create .codecraft/jobs/<name>.md and open the editor: settings with
a graphical cron builder (next runs in server time via /jobs/schedule), the
instructions in the Markdown editor and an assistant chat
(POST /jobs/{id}/assistant) whose model edits the file; the editor reloads it
after each turn and warns about conflicts with unsaved edits.
- The schedule tool writes prompt-only files with settings.
Chat list
- Folders and projects keep a user-defined order and can be pinned (drag and
drop, or the group's menu), stored per user via /account/sidebar. A new
message moves the chat to the top of its group, no longer the project itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
872ebb94dd
commit
05c215f685
19 files changed
+1661
-356
No files matched your search
@@ -3,6 +3,28 @@
|
||||
All notable changes to CodeCraft. Versions follow [Semantic Versioning](https://semver.org/);
|
||||
until 1.0, minor versions may contain breaking changes.
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **Automation editor:** *New automation* asks for name, project and a starting point (blank
|
||||
example structure or a template), creates `.codecraft/jobs/<name>.md` and opens an editor:
|
||||
the instructions in a Markdown editor, schedule and settings next to them, and an assistant
|
||||
chat in which a model works out the instructions with you and edits the file (reloaded after
|
||||
each answer). New automations start switched off.
|
||||
- **Graphical schedule:** every few minutes, hourly, daily, on weekdays, monthly or a cron
|
||||
expression, with the next runs in server time.
|
||||
- **Chat list:** folders and projects can be dragged into any order or moved and pinned to the
|
||||
top via their menu; the order is kept per user on all devices. A new message moves the chat
|
||||
to the top of its folder or project, no longer the whole project.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Automation files hold only the instructions;** name, schedule, mode, model, approval mode
|
||||
and time limit are settings of the automation. Existing job files are taken over on the first
|
||||
start (settings into the database, the frontmatter removed from the file). Registering a
|
||||
plain Markdown file creates a switched-off automation to be scheduled in the editor.
|
||||
|
||||
## [v202611-00012] – 2026-11-10
|
||||
|
||||
### Added
|
||||
|
||||
Reference in new issue
Block a user