All apps

First-party app · Mail Inbox

mail-inbox

IMAP mail as an inbox source. Polls a mailbox, surfaces messages from a fail-closed sender allowlist as inbox items, reads multipart and HTML mail, and hands each attachment to the Inbox as a file to list and download. Purpose-specific addresses can each carry a stored prompt, so mail to them runs it against the fenced mail body. Replies are composed as threaded drafts and are NOT sent until you turn sending on. Passwords are kept in the credential store, never in the settings file.

Before you install

A first-party app of PersonalClaw v0.3.9

No scan on record before install

PersonalClaw publishes no scan of its own apps before you install one.

PersonalClaw runs its own scan of the actual code of every app it installs: this one is rescanned when you install, and that scan is what can stop an install.

Its row on Compare: install rescan

Compatibility
Works with PersonalClaw v0.3.9

What it gets

Permissions
  • storage: true
  • network: true
Its own network permission
On. Its own network permission is a declaration, not a fence.

What it reaches

Hosts it names
Not declared in this release's manifest

Its own code has no host list at this release: any hosts it names are for the programs, servers and sources it starts or fetches, not everything it can reach. Its own network permission is a declaration, not a fence.

Secrets you would enter

Settings marked secret
  • IMAP Password
  • SMTP Password

The app's settings file holds only a reference, the value lives in the credential store, and every route that shows settings masks it. The app's own code receives the value when it runs.

Its own code calls PersonalClaw's gateway with a token scoped to the app, not with your owner token.

What installing it gives and runs

The manifest's own declarations, under the names install consent shows them by and in its order. The Store adds, at install, which of them run as you.

Permissions it is granted
{
  "storage": true,
  "network": true
}
Provider modules the gateway loads
[
  {
    "type": "inbox",
    "implementation": "mail_inbox_runtime.provider:create_provider"
  }
]
What it runs for personalclaw setup
"cli_setup:run"
What it runs for personalclaw doctor
"cli_doctor:probe"

Not declared in this release's manifest:

  • Scheduled jobs
  • Python packages installed for it
  • Engine packages it can install
  • What it needs that PersonalClaw does not install
  • Programs on this machine it starts
  • npm packages installed for it
  • Places outside its folder it writes
  • Pages it adds to the dashboard
  • Components it adds to the dashboard
  • A server process of its own
  • The sandbox tier its server runs in
  • Command run after install
  • Command run after an update
  • Command run when it is switched on
  • Command run when it is switched off
  • Command run before it is removed
  • Connector sources it parses
  • MCP servers it adds
  • Skills it installs

Where it comes from

Publisher
PersonalClaw
License
MIT
Pinned commit
169cbc4f8fc59cd42a65a6a3546235bc49ab3b22
Signer
Not declared in this release's manifest

From review to enable

  1. Held and scanned. An install stages the app in quarantine, checks its signature, and runs the shared supply-chain scanner over the staged bytes before anything is shown for consent. A registry's recorded verdict is not read at install: the scan that can stop it is this one.Its row on Compare: install rescan
  2. A dangerous verdict ends it. A dangerous verdict returns a refusal before consent is asked, so there is no consent to give and no switch that skips it. A warning verdict asks for your consent instead.Its row on Compare: dangerous verdict
  3. You review and consent. The review records a digest of the staged bytes, and an install committed against different bytes is refused: it needs consent again, because the app changed after it was reviewed. An update that changes what the app gets asks for consent again too.Its row on Compare: consent
  4. Its setup runs, then you switch it on. Nothing it declares runs before your consent; an app already installed is offered as an update instead.

To install it and switch it on

  1. In PersonalClaw, open the Store.
  2. Find mail-inbox.
  3. Review what it gets and runs, and consent.
  4. Install it, then switch it on.

Evidence

mail-inbox/app.json at the pinned commit, as written, with the blob hash git lists for it: 809a7ad0319f41a37c138b10e91e63a0064fca38

Open it at the commit

{
  "name": "mail-inbox",
  "version": "0.1.7",
  "displayName": "Mail Inbox",
  "description": "IMAP mail as an inbox source. Polls a mailbox, surfaces messages from a fail-closed sender allowlist as inbox items, reads multipart and HTML mail, and hands each attachment to the Inbox as a file to list and download. Purpose-specific addresses can each carry a stored prompt, so mail to them runs it against the fenced mail body. Replies are composed as threaded drafts and are NOT sent until you turn sending on. Passwords are kept in the credential store, never in the settings file.",
  "icon": "Mail",
  "author": "PersonalClaw",
  "license": "MIT",
  "requiresCoreFeatures": [
    "message-instructions"
  ],
  "tags": [
    "inbox",
    "email"
  ],
  "cli": {
    "setup": "cli_setup:run",
    "doctor": "cli_doctor:probe"
  },
  "permissions": {
    "storage": true,
    "network": true
  },
  "provider": {
    "id": "inbox",
    "label": "Your mailbox as inbox items",
    "type": "inbox",
    "implementation": "mail_inbox_runtime.provider:create_provider",
    "capabilities": [
      "poll",
      "attachments",
      "send"
    ],
    "settingsSchema": {
      "type": "object",
      "properties": {
        "host": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "IMAP Host",
            "help": "IMAP server hostname (e.g. imap.gmail.com)."
          }
        },
        "port": {
          "type": "integer",
          "default": 993,
          "x-meta": {
            "label": "IMAP Port",
            "help": "IMAP port. 993 for implicit SSL (the default); usually 143 with Use SSL off."
          }
        },
        "use_ssl": {
          "type": "boolean",
          "default": true,
          "x-meta": {
            "label": "Use SSL",
            "help": "Connect with implicit TLS (IMAP4_SSL). Leave on for port 993. Off, the connection is upgraded with STARTTLS before the password is sent, and a server that does not offer STARTTLS is refused: the password is never sent in the clear."
          }
        },
        "username": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "Username",
            "help": "IMAP login (usually the full email address)."
          }
        },
        "password": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "IMAP Password",
            "help": "An app-specific password (e.g. a Gmail App Password), never your account password. Kept in the credential store, never in the settings file; uninstalling the app removes it.",
            "sensitive": true
          }
        },
        "address": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "Receiving Address",
            "help": "The address mail arrives at — used as the inbox channel id. Defaults to the username when blank."
          }
        },
        "folder": {
          "type": "string",
          "default": "INBOX",
          "x-meta": {
            "label": "Folder",
            "help": "IMAP folder/mailbox to poll."
          }
        },
        "allow_senders": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "default": [],
          "x-meta": {
            "label": "Allowed Senders",
            "help": "Glob patterns of From addresses permitted to trigger (e.g. alerts@*.example.com). EMPTY means fail-closed — nothing is surfaced at all."
          }
        },
        "send_enabled": {
          "type": "boolean",
          "default": false,
          "x-meta": {
            "label": "Send Replies (off = draft only)",
            "help": "OFF by default. While off, every reply is composed as a real threaded draft under the app's data dir (drafts/*.eml) and NOTHING is sent — no SMTP connection is even opened. Turn this on only when you want this app to send mail as you: a sent email is irreversible and leaves your machine. Sending also needs the SMTP settings below, the SMTP password included, and it is still suppressed while the platform's live-writes guard (PERSONALCLAW_DISABLE_LIVE_WRITES) is set."
          }
        },
        "smtp_host": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "SMTP Host",
            "help": "Outbound SMTP server for replies (e.g. smtp.gmail.com). Blank means replies can only ever be drafted."
          }
        },
        "smtp_port": {
          "type": "integer",
          "default": 587,
          "x-meta": {
            "label": "SMTP Port",
            "help": "587 for STARTTLS (the default), 465 for implicit TLS."
          }
        },
        "smtp_security": {
          "type": "string",
          "enum": [
            "starttls",
            "ssl"
          ],
          "default": "starttls",
          "x-meta": {
            "label": "SMTP TLS Mode",
            "help": "starttls (587) upgrades the connection before the login and the mail, and refuses a server that does not offer it or an upgrade that fails: nothing is sent in the clear. ssl (465) is implicit TLS. Any other value reads as starttls."
          }
        },
        "smtp_username": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "SMTP Username",
            "help": "SMTP login. Blank reuses the IMAP username (same account). The SMTP password is never reused that way: it is its own setting, below."
          }
        },
        "smtp_password": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "SMTP Password",
            "help": "The password replies are sent with. A secret of its own: a blank one is never filled in from the IMAP password, so paste the same app password here if your provider uses one for both. Kept in the credential store, never in the settings file.",
            "sensitive": true
          }
        },
        "tls_ca_file": {
          "type": "string",
          "default": "",
          "x-meta": {
            "label": "CA Certificate File",
            "help": "Only for a mail server whose certificate comes from your own certificate authority: the path to that authority's certificate (PEM). It is trusted as well as this machine's own authorities. The server's certificate and name are always checked, and a server nothing vouches for is refused before a password is sent."
          }
        },
        "bound_addresses": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              },
              "address": {
                "type": "string"
              },
              "default_prompt": {
                "type": "string",
                "x-meta": {
                  "instruction": true
                }
              },
              "enabled": {
                "type": "boolean",
                "default": true
              },
              "allow_senders": {
                "type": "array",
                "items": {
                  "type": "string"
                }
              }
            },
            "required": [
              "address",
              "default_prompt",
              "allow_senders"
            ]
          },
          "default": [],
          "x-meta": {
            "label": "Prompt-Bound Addresses",
            "help": "Purpose-specific receiving addresses, each carrying a stored prompt. Mail to one runs that prompt against the mail body, which is always fenced as untrusted data. One JSON object per address: {\"name\": \"Business Travel\", \"address\": \"you+travel@gmail.com\", \"default_prompt\": \"Build my itinerary and add calendar entries.\", \"enabled\": true, \"allow_senders\": [\"*@booking.example.com\"]}. allow_senders NARROWS the Allowed Senders list above — it never widens it, and an EMPTY list fires nothing (fail-closed). No secrets here: the passwords are settings of their own, kept in the credential store."
          }
        }
      }
    }
  }
}
Scan verdict
No scan on record before install
Scan time
No scan is published before install
Blocking findings
No scan is published before install
Scanner version
No scan is published before install

PersonalClaw publishes no scan of its own apps before you install one.

  • Every app is scanned again when you install it, whatever its listing says.

    An install stages the app in quarantine, checks its signature, and runs the shared supply-chain scanner over the staged bytes before anything is shown for consent. A registry's recorded verdict is not read at install: the scan that can stop it is this one.

    apps/app_manager.py at v0.3.9
  • A dangerous scan verdict stops the install, and nothing overrides it.

    A dangerous verdict returns a refusal before consent is asked, so there is no consent to give and no switch that skips it. A warning verdict asks for your consent instead.

    apps/app_manager.py at v0.3.9
  • Consent covers exactly what you reviewed, and an app that changed asks again.

    The review records a digest of the staged bytes, and an install committed against different bytes is refused: it needs consent again, because the app changed after it was reviewed. An update that changes what the app gets asks for consent again too.

    apps/app_manager.py at v0.3.9
  • A setting an app marks secret is kept in the credential store and never shown back.

    The app's settings file holds only a reference, the value lives in the credential store, and every route that shows settings masks it. The app's own code receives the value when it runs.

    apps/secret_fields.py at v0.3.9

PersonalClaw/PersonalClawApps @ 169cbc4f8fc5 · mail-inbox/app.json