- Bubbles: own messages right-aligned in their own colour, agent answers left.
- Chat icons (22, validated on the server), shown in list, top bar, project page.
- Colour tags: eight fixed hues (new: pink) with theme-matched lightness and the
highest chroma sRGB allows; stronger background tint.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Claude Code as an engine: chats on a "claude-code/<alias>" model run through
the claude CLI (stream-json); tool approvals go through our permission
system. Sign in from the web UI (URL + pasted code), CLI version and update
from Settings; the Docker image contains the CLI.
- Small models (8k context) for side tasks: input is cut to the model's
context window; one-line chat status, "What does this do?" on approvals,
"Plan as automation" (job draft from a chat).
- Mobile: top bar no longer widens the page, image viewer (zoom, swipe, mark
up, use in message), jump to previous own message, message menu, time under
every message.
- Approvals: push actions (allow/reject), "always allow in this project"
(never for dangerous commands) with revoke.
- Per turn: changed files with diffs and rollback; project check command with
a green/red badge and "let the agent fix it".
- Colour tags for chats in the colours of the active theme.
- Project defaults for new chats, project page (timeline), offline queue.
Tested in a throwaway container with a mock model (8k small model): 26 API
checks passed (permissions, diffs, checks, defaults, job draft, side-task
budget, Claude Code status/login URL, unsigned-in chat).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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>
- Automations: the approval mode is a selection in the list; PATCH /jobs/{id}
writes permission_mode into the job file's frontmatter (rest of the file
unchanged, invalid modes rejected). "Allow everything" lets nightly runs work
without waiting for approvals via Telegram until the timeout.
- Session.telegram_quiet: approvals and questions of a chat (and its subagents)
are not sent to Telegram; the chat open in Telegram always reports. Toggle in
the chat's ⋯ menu when a bot is paired. New chats from the web UI and
automation runs start quiet; chats started from Telegram and existing chats
keep reporting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Daily backups (database + config) into <data_dir>/backups, keep N,
optional upload to any S3-compatible bucket (SigV4, bucket pruning);
settings panel with run-now, list and download
- Daily cost summary push at 20:00 (opt-in per user, preview button)
- Automations from templates (dependency check, security review, test
health, daily summary, TODO report, docs freshness) via POST /jobs/create
- browser tool: headless Chromium over CDP – click, type, keys, waits,
JavaScript, navigation, screenshots, console errors; requests to private
network addresses are blocked (sub-resources and redirects included)
- Secrets masked in the config view: S3 secret key, metrics token
- Replace the remaining text arrows/refresh glyphs with SVG icons
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- PWA share target: shared text/links start a new chat or go into a
recent session (chooser dialog)
- Prompt templates (personal + global for admins) with {{placeholders}}
that are asked for on insert; managed under Settings → Templates
- Ctrl/Cmd+K command palette; Alt+N new session, Alt+Up/Down switch
sessions, Ctrl+, settings
- Sessions can be pinned, archived and filed into folders; the list can
be grouped by date or by project, groups are collapsible
- Fix: the "What's new" dialog was never shown to signed-in users
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Webhooks for automations: per-job secret, Gitea/GitHub HMAC signatures,
payload appended to the instructions; settings on the automations page
- Service worker gets a new file name per build (proxies that cache *.js
served a stale worker, which broke updates and Android installation);
/sw.js is a kill switch that removes old workers
- Push: devices re-register their subscription with the server on start and
before a test; the test reports why a push service rejected a message
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Isolated git worktree per session (create, status, merge, discard)
- Permission card: accept file-edit hunks individually; agent learns what was rejected
- Reasoning effort per message; regenerate the last answer with another model/effort
- Voice input via the Web Speech API
- Folder-up button in the file browser; ssh, rsync and mc in the image
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Web terminal (PTY over WebSocket, xterm.js, sandboxed, reattach with replay)
- Per-user git credentials and commit identity (credential store in the user's home)
- OpenSCAD tool (STL/3MF + preview renders, bounding box) and cad skill; 3D model card
- Craft phase inferred from tool activity when the agent does not report it
- Configurable review loop per mode (rounds, reviewer model, criteria)
- Delete config and Markdown agents from the agent editor
- Automations: cron-scheduled agents from Markdown job files, schedule tool, page
- change_directory tool (only on the user's request)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Richard ZinkandClaude Sonnet 5.5
Richard ZinkandClaude Opus 5.5