First-party app · Email Channel
email-channel
Two-way email channel over stdlib IMAP/SMTP. Converse with your agent by email, replies thread back, and results arrive in the same conversation. No streaming; approvals answer by reply token.
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 App Password
- SMTP App 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": "channel", "implementation": "email_runtime.transport:create_provider" }, { "type": "trigger_source", "implementation": "email_runtime.trigger_source: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
- 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
- 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
- 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
- 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
- In PersonalClaw, open the Store.
- Find email-channel.
- Review what it gets and runs, and consent.
- Install it, then switch it on.
Evidence
email-channel/app.json at the pinned commit, as written, with the blob hash git lists for it: c62bf66d14d74c11e95814aca67647eb389b9a88
{
"name": "email-channel",
"version": "0.1.19",
"displayName": "Email Channel",
"description": "Two-way email channel over stdlib IMAP/SMTP. Converse with your agent by email, replies thread back, and results arrive in the same conversation. No streaming; approvals answer by reply token.",
"icon": "Mails",
"author": "PersonalClaw",
"license": "MIT",
"requiresCoreFeatures": [
"approval-answers",
"messages-run-once"
],
"tags": [
"channel",
"email",
"bundled"
],
"cli": {
"setup": "cli_setup:run",
"doctor": "cli_doctor:probe"
},
"permissions": {
"storage": true,
"network": true
},
"provider": {
"id": "channel",
"label": "Chat with your agent by email",
"type": "channel",
"implementation": "email_runtime.transport:create_provider",
"capabilities": [
"messaging",
"threads",
"attachments"
],
"settingsSchema": {
"type": "object",
"properties": {
"imap_host": {
"type": "string",
"default": "",
"x-meta": {
"label": "IMAP Host",
"help": "IMAP server hostname for inbound mail (e.g. imap.gmail.com)."
}
},
"imap_port": {
"type": "integer",
"default": 993,
"x-meta": {
"label": "IMAP Port",
"help": "993 for implicit SSL (the default), usually 143 with Use SSL off (upgraded with STARTTLS)."
}
},
"imap_user": {
"type": "string",
"default": "",
"x-meta": {
"label": "IMAP Username",
"help": "IMAP login, usually the full email address."
}
},
"imap_password": {
"type": "string",
"default": "",
"x-meta": {
"label": "IMAP App Password",
"help": "An app password from your mail provider, never your account password. Kept in the credential store and removed when you uninstall this app.",
"sensitive": true
}
},
"imap_use_ssl": {
"type": "boolean",
"default": true,
"x-meta": {
"label": "IMAP 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."
}
},
"folder": {
"type": "string",
"default": "INBOX",
"x-meta": {
"label": "Folder",
"help": "IMAP folder to poll. Polled read-only — your mail is never marked read."
}
},
"smtp_host": {
"type": "string",
"default": "",
"x-meta": {
"label": "SMTP Host",
"help": "SMTP server hostname for outbound mail (e.g. smtp.gmail.com)."
}
},
"smtp_port": {
"type": "integer",
"default": 587,
"x-meta": {
"label": "SMTP Port",
"help": "587 for STARTTLS (the default), 465 for implicit SSL."
}
},
"smtp_user": {
"type": "string",
"default": "",
"x-meta": {
"label": "SMTP Username",
"help": "SMTP login, usually the full email address."
}
},
"smtp_password": {
"type": "string",
"default": "",
"x-meta": {
"label": "SMTP App Password",
"help": "Leave empty to reuse the IMAP app password, which is what one app password does at Gmail, Fastmail and iCloud. Kept in the credential store and removed when you uninstall this app.",
"sensitive": true
}
},
"smtp_security": {
"type": "string",
"default": "starttls",
"enum": [
"starttls",
"ssl"
],
"x-meta": {
"label": "SMTP Security",
"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."
}
},
"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 the password is sent."
}
},
"address": {
"type": "string",
"default": "",
"x-meta": {
"label": "Mailbox Address",
"help": "The address this channel sends as and receives at. Defaults to the IMAP username. Also the self-message filter's anchor."
}
},
"poll_secs": {
"type": "integer",
"default": 60,
"x-meta": {
"label": "Poll Interval (s)",
"help": "How often to check for new mail. Clamped to 10-3600s."
}
},
"dm_activation": {
"type": "string",
"default": "always",
"enum": [
"always",
"off"
],
"x-meta": {
"label": "Inbound Activation",
"help": "always answers every paired sender; off disables inbound while keeping outbound delivery."
}
}
}
}
},
"providers": [
{
"id": "triggers",
"label": "Run automations when mail arrives",
"type": "trigger_source",
"implementation": "email_runtime.trigger_source:create_provider",
"capabilities": [
"mail_received"
]
}
]
}
- 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.9A 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.9Consent 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.9A 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 · email-channel/app.json