Skip to content
Motir
Start free

moooon

Motir

Vibe your whole project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.

  • Vibe Project
  • Open Source
  • AI Agent
  • AI Loop
1
requests
0
upvotes
145
planned
1,361
shipped
Follow  — continues on app.motir.co
Request a featureAtom feed

← Motir · Work items

MOTIR-2110Done

BUG (motir-core) — the re-plan job envelope omits `generateExplanations`, so the project's "AI-drafted explanations" setting silently does nothing on re-plan

Repo: motir-core. One PR. The PRODUCER half of a two-repo contract gap; the consumer half is its dependent card.

The defect

aiGenerationService.generateTree puts the project's opt-in on the wire — generateExplanations: ctx.project.aiGenerateExplanations in the generate_tree job envelope's context — with a comment stating that motir-ai reads it from context.generateExplanations and never reads core config directly. The re-plan submit path does not send that field at all.

Consequence: a project that has turned AI-drafted explanations ON in /settings/project/ai-planning gets a per-node "why this matters" on a fresh generation, and nothing on a re-plan — the setting reads as global but is silently generation-only. Because the flag rides the envelope by design, motir-ai cannot compensate; if core does not send it, the re-planner cannot know.

Verified on origin/main (2026-08-04): git grep generateExplanations in lib/ returns the settings editor, lib/ai/types.ts, and the generate_tree submit — and no re-plan submit site.

Acceptance criteria

  • The re-plan job submit sends context.generateExplanations from ctx.project.aiGenerateExplanations, exactly as the generate_tree submit does — same field name, same source, no new config path.
  • The envelope type (lib/ai/types.ts) admits the field on the re-plan request shape, and a test asserts the submitted envelope carries it for a project with the setting ON, and the value false (not an omission that reads as "unset") when OFF — match whatever discipline generate_tree already uses for the OFF case.
  • No behaviour change on generate_tree.
  • Because this is the producer half of a boundary contract, the PR body names the consumer card so the two land in order.
  • PR title carries MOTIR-<id>.

Context refs

  • lib/services/aiGenerationService.ts — the generate_tree submit that DOES send it (the shape to copy) and the re-plan submit that does not.
  • lib/ai/types.ts — the job-envelope context type carrying generateExplanations.
  • app/(authed)/settings/project/ai-planning/_components/AiPlanningSettingsEditor.tsx — the user-facing toggle whose promise is currently half-kept.
  • motir-ai/src/jobs/handlers/replan.ts — the consumer that must then read it (the dependent card).