← newsletter

DevLog #21: Save Multiple Accounts, Control Slack Replies, and Check Subscription Usage

Save accounts and check their remaining allowance

• Keep multiple Claude and ChatGPT accounts connected. Admins can add and name accounts in Integrations, reconnect a specific account, and choose the default for new sessions. Running sessions keep their assigned account when the default changes. Adding a backup preserves your existing default. Accounts are shared with your organization, and selection is manual.
• Check reported subscription usage for each account. The account cards show remaining allowance, reset times, and when the reading was received. Allowance at 10% or less is highlighted. Readings come from supported Slack, Discord, and automation sessions when the provider reports usage. Missing readings are labeled; unused backup accounts may show an older reading or no reading. Claude limit notices can now appear even when the agent reaches its limit before producing an answer.

Connect an API provider and choose its coding agent

• Configure OpenRouter, Fireworks AI, or Subconscious from Integrations. Save the connection, choose one compatible coding agent, and discover models or enter a model ID manually. The form keeps the API format, model, and agent choice together. OpenRouter and Fireworks AI also support the Anthropic Messages format for Claude Code; model compatibility still depends on the provider.

Choose when the agent responds in Slack

• Discuss work in an active thread and mention the agent when you want a response. Run !tagonly on to require mentions in that thread. Nori saves up to 100 recent untagged messages for the next explicit mention. Use !tagonly off to resume responses to all replies, or !tagonly default to follow the inherited setting. Admins can set an organization default under Security → Slack replies and override it for a custom agent.
• Have automated jobs send you a one-to-one Slack message or file. Jobs with wildcard Slack access can open a direct message by user ID and deliver their output there. Reading direct-message history and accessing group direct messages remain blocked.

Review and run automations from one panel

• Check an automation’s schedule, instructions, agent, delivery destination, and latest result from its card. Open the card to edit or run it in a shared side panel. Admins can review proposed changes there, including the previous and proposed values. Webhook test runs accept a JSON payload, and errors appear beside the action that failed.

Choose your theme and finish saving settings

• Choose Light, Dark, or Auto from the dashboard sidebar. Auto follows your operating system’s theme, and your preference is saved in the browser. Follow-up fixes make integration logos, activity tooltips, onboarding text, and alert banners readable in their selected theme.
• See settings and credential saves complete when the changes are stored. Forms could stay on “Saving…” while Nori prepared sessions, distributed credentials, or refreshed version history. That follow-up work now continues in the background. Saved provider URLs and model fields also stay filled in when you reopen their forms.