Haruno Knowledge base

Approvals and permission modes

When Haruno wants to do something that needs your OK, a card appears in the chat with Allow once, Allow for this session and Deny. The permission mode decides how often that happens.

  • Mac appAvailableThe normal view is fixed at Automatic. The advanced view chooses the mode.
  • Windows appAvailableThe mode chip and the Default permission mode setting are only in the advanced view.

Before Haruno does something that needs your OK, it stops and shows a card in the chat. Nothing happens until you answer. This is the same in the normal view and the advanced view.

The approval card

An example card. The wording comes from what Haruno wants to do.
An approval card titled Run release checks with a Low risk label, the command npm test under Details, a short explanation, and three buttons: Allow once, Allow for this session and Deny.An approval card titled Run release checks with a Low risk label, the command npm test under Details, a short explanation, and three buttons: Allow once, Allow for this session and Deny.

A card shows:

  • what Haruno wants to do, for example run a command, read a file, create or overwrite a file or open a web page;
  • a risk label on some cards: Low risk, Medium risk or High risk;
  • Details, which opens to show the tool and the exact command or input;
  • a short explanation of why, when there is one.

Pick one of three buttons:

ButtonWhat it does
Allow onceLets this one action go ahead.
Allow for this sessionAllows this kind of action for the rest of the chat.
DenyRefuses it. Haruno is told and carries on without it.

After you answer, the card says Answered with your choice.

Some cards offer only Allow once and Deny. Actions that send data off the PC are one case. Some custom tools and browser actions are another. See Sending things outside.

What you see is what will run

The command under Details is shown exactly as written, never formatted. Links and pictures that appear in an explanation are shown as plain text and cannot be clicked, so a card cannot be used to lead someone to a page.

When the window is in the background

If Haruno is behind another window, or you are on a page other than Chat, Windows shows a Permission required notification. For most requests you can choose Allow once or Deny right there. For a high risk request, or one that does not fit in the notification, click it. Haruno opens and you answer the card. A notification never offers Allow for this session. You can turn these notifications off with Notifications in Settings ▸ General.

Always allowed

In the advanced view, each Allow for this session you give appears as a chip under Always allowed: in the Activities panel. The × on a chip, labeled Remove permission, takes that permission back.

Permission modes

The permission mode decides how Haruno treats actions that have no rule of their own.

  • Normal view. The mode is locked to Auto. There is no chip and no choice.
  • Advanced view. A mode chip sits above the message box. Click it and choose a mode. The chip is hidden in Ask mode, which is a chat without tools.
The permission mode menu in the advanced view.
The advanced chat with the permission mode menu open above the message box. The choices are Default, Accept Edits, Plan, Auto and Bypass, and Auto is ticked.The advanced chat with the permission mode menu open above the message box. The choices are Default, Accept Edits, Plan, Auto and Bypass, and Auto is ticked.
ModeWhat it means
DefaultAsks before actions that need approval.
Accept EditsFile edits and simple file commands, such as creating, moving, copying or deleting files, go ahead. Other actions still ask.
PlanHaruno works out a plan before changing anything. You choose Approve plan, Request changes or Reject plan.
AutoHaruno judges which actions are safe and lets those go ahead without asking.
BypassActions go ahead without asking, except tools set to Confirm and a few safety checks.
In Plan mode Haruno shows its plan first and waits for you.
A plan card titled Release plan with two steps and three buttons: Approve plan, Request changes and Reject plan.A plan card titled Release plan with two steps and three buttons: Approve plan, Request changes and Reject plan.

New chats start in the mode set in Settings ▸ Advanced ▸ Default permission mode. Picking a mode with the chip changes that setting too, so the mode you used last is where the next chat starts.

Bypass

In Bypass, actions go ahead without a card, including a command that sends data off the PC. It is meant for a folder the customer is happy for Haruno to change freely, in a chat they are watching. It is not offered in the normal view.

When Auto is not available

In some chats Haruno cannot use Auto. It then starts the chat in Default, shows a note saying why, and the menu stops offering Auto from then on.

Tools set to Confirm

A connector tool can be set to On, Off or Confirm in Settings. Confirm always asks, even in Auto. Use it for anything that acts for you in the outside world, such as sending a message or posting.

When nobody is there

A scheduled task or a hook has nobody to answer a card. A tool set to Confirm is refused instead of waiting. Anything that would send data off the PC is refused too. See Sending things outside.

Last updated · PR #2944 · View this version on GitHub

History (1 version)
  1. Internal knowledge base for staff: site, reader keys, assistant, 197 pages and the PR rule (#2944)
    What changed
    @@ -0,0 +1,85 @@
    +---
    +title: Approvals and permission modes
    +summary: When Haruno wants to do something that needs your OK, a card appears in the chat with Allow once, Allow for this session and Deny. The permission mode decides how often that happens.
    +feature: permissions
    +covers:
    +  - windows-client/haruno-webview/web/src/components/chat/DecisionCards.tsx
    +  - windows-client/haruno-webview/web/src/components/chat/chatEventStrings.ts
    +  - windows-client/haruno-webview/web/e2e/permission-mode-menu.spec.ts
    +  - windows-client/haruno-webview/web/e2e/chat-permission-markdown.spec.ts
    +  - windows-client/Haruno.Desktop.ViewModels/ChatViewModel.cs
    +---
    +
    +Before Haruno does something that needs your OK, it stops and shows a card in the chat. Nothing happens until you answer. This is the same in the normal view and the advanced view.
    +
    +## The approval card
    +
    +<Shot src="/m/b38c2d9b29c6-windows-safety-approval-card-light.png" dark="/m/62cf71c52a04-windows-safety-approval-card-dark.png" alt="An approval card titled Run release checks with a Low risk label, the command npm test under Details, a short explanation, and three buttons: Allow once, Allow for this session and Deny." caption="An example card. The wording comes from what Haruno wants to do." />
    +
    +A card shows:
    +
    +- what Haruno wants to do, for example **run a command**, **read a file**, **create or overwrite a file** or **open a web page**;
    +- a risk label on some cards: **Low risk**, **Medium risk** or **High risk**;
    +- **Details**, which opens to show the tool and the exact command or input;
    +- a short explanation of why, when there is one.
    +
    +Pick one of three buttons:
    +
    +| Button | What it does |
    +|---|---|
    +| <Ui>Allow once</Ui> | Lets this one action go ahead. |
    +| <Ui>Allow for this session</Ui> | Allows this kind of action for the rest of the chat. |
    +| <Ui>Deny</Ui> | Refuses it. Haruno is told and carries on without it. |
    +
    +After you answer, the card says **Answered** with your choice.
    +
    +Some cards offer only **Allow once** and **Deny**. Actions that send data off the PC are one case. Some custom tools and browser actions are another. See [Sending things outside](/windows/safety/sending-data-out/).
    +
    +<Callout variant="info" title="What you see is what will run">
    +The command under Details is shown exactly as written, never formatted. Links and pictures that appear in an explanation are shown as plain text and cannot be clicked, so a card cannot be used to lead someone to a page.
    +</Callout>
    +
    +### When the window is in the background
    +
    +If Haruno is behind another window, or you are on a page other than Chat, Windows shows a **Permission required** notification. For most requests you can choose **Allow once** or **Deny** right there. For a high risk request, or one that does not fit in the notification, click it. Haruno opens and you answer the card. A notification never offers **Allow for this session**. You can turn these notifications off with **Notifications** in <Ui>Settings ▸ General</Ui>.
    +
    +### Always allowed
    +
    +In the advanced view, each **Allow for this session** you give appears as a chip under **Always allowed:** in the Activities panel. The **×** on a chip, labeled **Remove permission**, takes that permission back.
    +
    +## Permission modes
    +
    +The permission mode decides how Haruno treats actions that have no rule of their own.
    +
    +- **Normal view.** The mode is locked to **Auto**. There is no chip and no choice.
    +- **Advanced view.** A mode chip sits above the message box. Click it and choose a mode. The chip is hidden in **Ask** mode, which is a chat without tools.
    +
    +<Shot src="/m/646ef346b5c0-windows-safety-permission-menu-light.png" dark="/m/1b3fe4a133bf-windows-safety-permission-menu-dark.png" alt="The advanced chat with the permission mode menu open above the message box. The choices are Default, Accept Edits, Plan, Auto and Bypass, and Auto is ticked." caption="The permission mode menu in the advanced view." />
    +
    +| Mode | What it means |
    +|---|---|
    +| **Default** | Asks before actions that need approval. |
    +| **Accept Edits** | File edits and simple file commands, such as creating, moving, copying or deleting files, go ahead. Other actions still ask. |
    +| **Plan** | Haruno works out a plan before changing anything. You choose **Approve plan**, **Request changes** or **Reject plan**. |
    +| **Auto** | Haruno judges which actions are safe and lets those go ahead without asking. |
    +| **Bypass** | Actions go ahead without asking, except tools set to **Confirm** and a few safety checks. |
    +
    +<Shot src="/m/dd46c5addb3b-windows-safety-plan-card-light.png" dark="/m/9ae326c20ec7-windows-safety-plan-card-dark.png" alt="A plan card titled Release plan with two steps and three buttons: Approve plan, Request changes and Reject plan." caption="In Plan mode Haruno shows its plan first and waits for you." />
    +
    +New chats start in the mode set in <Ui>Settings ▸ Advanced ▸ Default permission mode</Ui>. Picking a mode with the chip changes that setting too, so the mode you used last is where the next chat starts.
    +
    +<Callout variant="warning" title="Bypass">
    +In Bypass, actions go ahead without a card, including a command that sends data off the PC. It is meant for a folder the customer is happy for Haruno to change freely, in a chat they are watching. It is not offered in the normal view.
    +</Callout>
    +
    +<Callout variant="info" title="When Auto is not available">
    +In some chats Haruno cannot use Auto. It then starts the chat in Default, shows a note saying why, and the menu stops offering Auto from then on.
    +</Callout>
    +
    +## Tools set to Confirm
    +
    +A connector tool can be set to **On**, **Off** or **Confirm** in Settings. **Confirm** always asks, even in Auto. Use it for anything that acts for you in the outside world, such as sending a message or posting.
    +
    +## When nobody is there
    +
    +A scheduled task or a hook has nobody to answer a card. A tool set to **Confirm** is refused instead of waiting. Anything that would send data off the PC is refused too. See [Sending things outside](/windows/safety/sending-data-out/).