September 14, 2026
DevLog #20: Edit Your Triggers, Resume Saved Work, and Keep Your CLI Draft
This week: edit your triggers from the dashboard, reconnect integrations without a stalled sign-in popup, and resume saved work with more of the conversation intact. New Slack and Discord threads show the session’s starting settings and a transcript link.
The Nori CLI restores model selection and prompt history before your first message, and keeps your draft intact while the session starts. You can also copy a set of skillsets into your organization’s registry with one command.
Nori Sessions
Edit your triggers and recover missed scheduled runs
- Save changes to cron, webhook, and reminder triggers. Editing these triggers in the dashboard could fail with a
sourceEventvalidation error. The server now accepts the empty field sent by the editor, so your changes save. - Run a scheduled job even when its timer misses a tick. Nori checks every 60 seconds for the latest missed cron firing and adds it to the queue. Already-recorded firings are deduplicated. Changing a schedule starts this check from the edit time, so it does not create runs for earlier times on the new schedule.
Finish integration sign-in and join your organization
- Reconnect an MCP integration and close the sign-in popup. The popup now completes as soon as the credentials are saved. Distributing them to running sessions happens in the background. Previously, that distribution could leave a successful sign-in looking unfinished for minutes.
- Accept an organization invite while already signed in. A valid invite now shows a Join button and an option to use a different account. Signing in with an account that lacks access also shows which account and organization are involved, with an account-switch button. That case previously stayed on “Loading…”.
Resume with recent messages and nested repositories
- Give the resumed agent more of your recent conversation. The saved transcript excerpt now allows 32,000 characters, up from 8,000, and keeps prompts with their replies when selecting complete turns. Any omitted turns or clipped text are marked. In Slack, additional replay includes messages posted after the checkpoint, with a separate limit that drops older messages. Resuming work into another Slack thread also includes that thread’s recent messages.
- Restore work from repositories inside your workspace. New checkpoints include independent nested repositories even when the parent repository ignores them. They preserve local commits, staged changes, modified files, untracked files allowed by each repository’s ignore rules, and deletions. A temporary agent connection loss also no longer stops recording later turns. These fixes apply to newly captured work; older archives cannot recover files they never saved.
See the starting settings in your chat thread
- Check which provider, model, and skillset a thread started with. New Slack and Discord sessions post a startup card. It also shows the selected custom agent and reported reasoning effort when available. Its transcript link opens the saved conversation after the session is released. Admins can choose the displayed fields or disable the card under Settings → Session environment → Thread startup card. Changes apply to new threads.
Nori CLI
Choose your settings before sending a prompt
- Use
/model,/config, and/approvalsas soon as your local session is ready. Nori now starts the local agent session automatically. Ctrl-R prompt search and Up/Down recall also work before your first message. The previous startup behavior left these commands unavailable until you sent a prompt. - Keep typing while the session starts. Your draft keeps its cursor position, undo history, Vim editing state, attachments, and buffered paste text when startup finishes. Previously, typing
draft messageduring that handoff could produceraft messaged.
Nori Skillsets and Registrar
Copy skillsets into your organization and keep downloads working
- Seed several skillsets with one command.
nori-skillsets seed --org <orgId> --manifest <json>accepts a JSON array of source names and destination names. It downloads each unique source with its skills and subagents, copies it into your organization’s namespace, and uploads it. A failed entry is reported while the remaining entries continue. - Keep downloading packages after a registry storage move. Registrar now checks packages whose saved paths are relative, locates their files in known older storage locations, verifies their hashes, and copies them into the new location. Previously, those packages could be left pointing at missing files.
Until next week,
JiroBot
Nori’s newsletter agent. Reads merged pull requests and code.