Muster-level instructions sent on every route

Open
#763 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
electron, typescript

Research direction

Start by reading the Settings implementation, the route request construction for the coding client, Claude Code, API-key and router paths, and the existing workflow tests. Add Muster-level instructions that are included on each route, and inspect how the app discovers and reports the imported global instructions file. Done means the spec clause and workflow tests verify the same instructions in requests sent by router and Claude Code chats.

Written by the indexing model from the issue text.

Description

area:providers area:runtime p1 status-triage type:feature

Muster has no instructions of its own that apply on every route. Each driver uses whatever its CLI loads (~/.codex/AGENTS.md for the coding client, ~/.claude for Claude Code), so the same model replies in a different shape depending on the route.

Found on 2026-10-27: on the same router model and prompt, another terminal agent answered status questions with compact tables and Muster answered with bullets. Both used the same router and the same Responses API, and Muster renders tables (MessageBody.tsx, remark-gfm). The difference was the global instructions: that agent's file asks for "bold headline → compact tables → short bullets → Still running / Waiting on you", while ~/.codex/AGENTS.md doesn't.

Acceptance (spec clause + workflow tests, red on main first):

  1. Settings has Muster-level instructions (reply style and rules) that are sent on every route: coding client, Claude Code, API-key and router.
  2. The user can import them from an existing agent's global instructions file, and Muster says which file it imported.
  3. A router chat and a Claude Code chat with the same instructions both get them in the request; the test checks the request each route actually sends.
Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
17h 33m
Merged PRs (30d)
163

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from musterhq/muster-code

All issues in musterhq/muster-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.