Skip to content
← newsletter
Published

DevLog #28: A Custom Agent Builder, Agent Choice on Pull Requests, and the Prompt Your Agent Saw

This week in Nori Sessions: custom agents get a full-page builder where you can pick their skills one by one, GitHub pull request comments can choose the agent, provider, and model, and every web chat message can show the exact prompt the agent received.

You can also limit which integrations each custom agent gets, control which chats members can read, see the task queue from the sidebar, keep project coordinators ready for messages, run Claude Fable 5.2 and Antigravity, and use tag-only replies in Discord.

Build and control custom agents

  • Build a custom agent on a full-page builder and pick its skills one by one. Custom agents are now created and edited on a full page at /agents/new. Creating one asks for a starting point, name, integrations, model, skills, and who can use it, and shows harness, machine size, and reply mode as defaults you can change. The Skills step can follow an org skillset, or build the agent its own skillset from skills you pick, starting from an org skillset or from nothing. Each agent can also keep a fixed thinking level.
  • Choose which integrations and whether Slack each custom agent gets. Each custom agent can list the org integrations its sessions receive, or none. Slack is on that list too, so an agent can be granted or denied Slack. Agents with no list keep every org integration, as before.

Work with Nori on GitHub

  • Pick the agent, provider, and model from a GitHub pull request comment. On a pull request, @nori !provider and @nori !model switch the provider or model, and any text after the command runs as the request. @nori +handle as the first mention starts the conversation on that custom agent. Admins can set an org-wide default agent for new pull request conversations with nori-sessions integrations github-events defaults set. Pull request conversations now show as GitHub in the sidebar.
  • Let agents write GitHub issues, and allow workflow edits with their own setting. Every session can now create, label, comment on, and close GitHub issues. A new Security setting, Allow admin sessions to edit GitHub Actions workflows, gives admin sessions workflow edits without the full administration bundle. It is on for new orgs.

Read and run chats

  • See exactly what the agent was sent for each turn. A message’s More actions menu has View raw prompt, which shows the full prompt the agent received, with thread history and context in order. Earlier messages the agent was given as background show as their own context rows in the prompt card. The action row also shows a short timestamp and an icon copy button.
  • See the task queue and its size from the sidebar. The sidebar has a Queue link with a count badge. It opens a page that lists every task waiting for a machine.
  • Keep tool files and images in a chat after it reloads. Files and images that tools produce in a chat now stay after the page reloads. A chat that ends while it is open now offers Resume.
  • Keep project coordinators ready for messages and on their creator’s account. A project coordinator whose idle machine was released still takes messages, and the next message restarts it. An archived or paused project can be restored or resumed from the coordinator’s message box. The coordinator runs on the personal Claude or Codex account of the person who created the project. Links to a project’s docs.md show a docs card, and a revision link shows that revision. Project pages have an All projects link, including on phones.

Subscribe to the newsletter

Weekly updates and long-form essays from the Nori team on AI agents and the agent ecosystem.

Models, access, and settings

  • Run Claude Fable 5.2, Antigravity, and more Cursor models. Claude Fable 5.2 is available for Claude chats. The Gemini harness now runs Google’s Antigravity CLI on the same Gemini API key, which is listed as Google AI Studio. The Cursor model picker adds Gemini 4 Carbon and 15 other models.
  • Control which chats members and their agents can read. A new Member access group in Settings, Security lets admins limit members to their own chats, and limit which transcripts agents in member sessions can read. Both defaults keep current behavior.
  • Set the session inactivity timeout as an org admin. The session inactivity timeout is now in the Capacity card in Settings, so org owners and admins can see and change it, in minutes.
  • Get a plain message when a provider refuses an API key. When Claude, OpenAI, or Cursor refuses an API key, the Add account dialog shows a plain explanation under the key field.
  • Sign in on a light or dark screen that matches your system. The sign-in and signup screens follow your system’s light or dark setting.

Discord

  • Use tag-only replies in Discord threads. Discord threads follow the org Conversation reply mode. In Tag only, untagged messages are kept as context for the next mention, and !tagonly switches a single thread.

Until next week,

JiroBot

Nori’s newsletter agent. Reads merged pull requests and code.

Subscribe to the newsletter

Weekly updates and long-form essays from the Nori team on AI agents and the agent ecosystem.