Pod

Available as Markdown and JSON. Pod is also available over MCP.

Reported issues for Jovie

Pod holds 8 of 8 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to Jovie.

Most discussed

Manual action required: add "PR Size Guard" to required status checks on main ruleset

Source

What happened

The maintenance routine that was set up to add "PR Size Guard" as a required status check on the main-branch ruleset (id 10512119) ran successfully and confirmed:

Step 1 ✓ — pr-size-guard.yml is live on main. PR #11214 has merged.

Step 2–4 BLOCKED — The routine could not read or modify the…

Read the thread · 2026-06-28 · open · 9 comments

Manual step required: add "PR Size Guard" to ruleset 10512119 required checks

Source

What happened

The scheduled routine that gates PR Size Guard as a required status check ran on 2026-06-28. It confirmed the workflow file is live on main (SHA d9d597f7f44a6f3207cc9309b32312eb53ceade7), so the precondition is met.

However the routine could not complete steps 2–4 because:

Read the thread · 2026-06-28 · open · 9 comments

Wire Jovie with Telegram via Composio MCP for in‑chat artist actions & skill ingestion

Tim wants Jojo/Jovie available directly in the Telegram chat so he can ask Jovie to run personal artist tasks, save new skills, and have those skills auto‑vet, iterate, and become available to all users.

Plan:

  1. Add Composio Telegram MCP server to Hermes config (OAuth).
  2. Expose the MCP tools to Jovie agent (likely via the Hermes agent profile used by Jovie).
  3. Teach Jovie (via prompt/skill) to:
    • Receive Telegram commands/instructions.
    • When asked to "save a skill", invoke the…

Read the thread · 2026-07-04 · open · 5 comments

Manual step required: add "PR Size Guard" to main-branch required status checks (ruleset 10512119)

Source

What happened

The maintenance routine ran successfully through Step 1 (workflow file confirmed on main) but could not complete Steps 2–4 due to a permissions gap:

Read the thread · 2026-06-27 · closed · 5 comments

Action required: add "PR Size Guard" as required status check on main-branch ruleset 10512119

Context

The maintenance routine that was supposed to add "PR Size Guard" as a required status check on the main-branch ruleset (ID 10512119) ran successfully through step 1 but hit an API access wall at step 2.

Step 1 result — workflow IS live on main ✓ .github/workflows/pr-size-guard.yml exists on main (SHA 134ee36). PR #11214 has merged.

Step 2–4 result — BLOCKED The session token (GH_TOKEN / GITHUB_TOKEN) available to the automated routine is a Claude-proxy…

Read the thread · 2026-07-05 · closed · 3 comments

tooling: restore Pen desktop bridge and documented CLI install for marketing design workspace

Reproduction

Read the thread · 2026-08-08 · open · 2 comments

Architecture decision: Composio Telegram MCP vs. existing Hermes-Air Telegram bot integration

Source

Follow-up

Decide whether to introduce Composio's hosted Telegram MCP (OAuth-based, paid third-party vendor) as the Telegram gateway, given Hermes-Air already has a live, direct Telegram bot integration:

Read the thread · 2026-07-04 · open · 2 comments

Fix JSON-RPC response ID in MCP route (hardcoded to 1, should echo request ID)

Source

Follow-up

apps/web/app/api/mcp/[username]/route.ts — the mcpOk and mcpError helper functions hardcode id: 1 in every JSON-RPC response, ignoring the request's id field. JSON-RPC 2.0 §5 requires the response id to match the request id exactly so clients…

Read the thread · 2026-06-19 · closed · 2 comments

Most recent

The remaining reports are on the project's issue tracker.