← newsletter

DevLog #26: One Chat Side Panel, Faster Phone Chats, and Conversations That Outlast Their Machine

Work with chats on the web and your phone

• Open artifacts, previews, the browser, the shell, and a Markdown export from one chat side panel. Each chat now has one side panel with Artifacts, Preview, Browser, Shell, and Export tabs. Export builds a Markdown copy of the whole conversation (your prompts and the agent’s final replies) that you can copy or download. On a phone, swipe to open and close the panel.
• Open a conversation in a moment on your phone, even when its history is long. The phone app paints right away and opens conversations with fewer round trips. Long conversations show their latest messages first and load older history in the background, and browsers reuse finished history pages for a day.
• Type your next message while a chat resumes, reconnects, or starts. The message box stays editable while a session resumes, reconnects, or starts. Send waits until the session is live and shows why it is waiting, and your draft is kept.

Keep long conversations and automations running

• Keep a long conversation going after its machine reaches its time limit. When a session machine nears its provider’s 24-hour limit, Nori restores the conversation onto a fresh machine at a turn boundary and carries on there, so the chat keeps working. A turn cut off by the move now ends cleanly in the chat with no stuck “Working…” spinner.
• See a clear end to a conversation whose machine is gone. When a conversation’s machine has been shut down by its provider, the chat now ends the conversation and stops showing “Reconnecting to your session…” forever.
• Set a time limit for automation runs. A new fleet setting caps how long an automation run may take (6 hours by default, from 1 minute to 24 hours). A machine with a turn in progress is never treated as idle, so busy automations are no longer reclaimed mid-run.
• Switch between your automations and everyone’s with one toggle. The automations page has one Yours/All switch in its header, so admins who wrote no automations of their own can still see the whole org’s.
• Turn on weekly test and helper cleanup automations. Two new built-in automations, off by default: test gardening adds a regression test or fixes a flaky test each Wednesday, and utils gardening moves a few call sites onto helpers your repo already has each Thursday. Teams that already finished setup are asked about new automations as they ship.

Set up your workspace and integrations

• Sign in with your Claude subscription during onboarding without opening a terminal. Picking a Claude subscription at signup no longer asks you to run claude setup-token yourself. Claude sign-in opens once your workspace is ready, and you can still paste an existing setup token.
• Get morning updates from Jiro during your team’s first week. On the first five weekday mornings after workspace setup, Jiro posts what it did the previous work day, or suggests up to three pieces of work for your repos. Reply to start one.
• Connect MCP servers that use client ID metadata documents, such as Affinity. MCP servers that support client ID metadata documents and have no dynamic client registration now connect through OAuth.
• Install the Nori Salesforce package from the Salesforce setup panel. The Salesforce panel now walks admins through installing the Nori Salesforce Connector package in production or sandbox, then asks them to confirm before connecting.

Models and agents

• Choose GPT-6.1 Terra for Codex sessions. GPT-6.1 Terra is in the Codex model list. GPT-5.5, which OpenAI retired from Codex, is gone, and Cursor’s Grok 4.5 option now carries its correct High label.
• Run Gemini CLI sessions with Nori’s settings applied. Nori’s Gemini CLI settings now take effect, so usage statistics and auto-update are off in every Gemini session, and file tools can read skills in gitignored folders.

Upload skillsets with nested skills

• Upload skillsets that contain nested skills. Uploading a skillset with nested skill or subagent folders (for example .system/imagegen) now works and no longer crashes the registrar.