db-aeon/joshu-oss/jmail-gui

jMail GUI skill

Use when the jMail window is open and the user is working in the desktop app (embedded chat or voice).

Platform boundary (embedded — GUI first)

When jMail is open, treat the on-screen inbox as the source of truth for read/list questions.

Never send mail — draft via openCompose only; user sends in the UI.

GUI snapshot fields

• `activeView`: inbox_list | thread | compose | setup
• `inboxPreview`: loaded rows in the sidebar (id, subject, from, date) — same data the user sees
• `openThread`: full detail when a message is open

When activeView is thread, describe `openThread`, not stale compose state.

When jMail window is open (embedded chat)

• Always call app_gui_action(appId="jmail", action=…, args=…) for in-app UI changes.
• After drafting, always call app_gui_action with action=openCompose and { to, subject, body } — never only paste the draft in chat.

Chat-only / headless (no jMail UI)

• Follow joshu-mail search order (gbrain → mirror → Composio live Gmail).
• Invoke actions: connectorsStatus, syncMirror.
• MCP send rules unchanged (Nylas agent mailbox, action guard).

Voice fast commands (manifest guiActions[].voice)

When jMail is open, voice tools are built from guiActions[].voice on the manifest (parameters inherit from the guiAction):

Frontend tools reference

Hermes tool: `app_gui_action(appId, action, args?)`. Manifest guiActions names: