Skip to content
OpenChamber
↑↓Navigate ↵Open escClose

Magic Prompts

OpenChamber uses built-in prompts behind the scenes whenever it does something automatically — writing a commit message, drafting a PR, reviewing an issue, resolving a conflict, summarizing a session. Magic Prompts is where you read and rewrite those prompts. Open it at Settings → Magic Prompts.

You don’t need this page for normal use. Reach for it when you want a flow to behave differently — say, commit messages in a particular style.

Edit a prompt

  1. Open Settings → Magic Prompts.
  2. Pick a prompt from the groups in the sidebar — Git, GitHub, Planning, and Session.
  3. Edit the text and save.

Some prompts have a visible part (the message you’d see) and an instructions part (hidden guidance for the agent). Prompts can include {{placeholders}} that OpenChamber fills in, like the diff or the issue title — keep those in place.

Reset

Changed your mind? Each prompt has reset to default, and there’s a reset all if you want to start over everywhere.

Where each prompt is used

Every prompt below lists where it runs and the trigger that fires it. Check the trigger before editing, so you know which flow you’re changing.

Git

PromptWhere it runsWhen it fires
Commit generationThe generate button in the git view’s commit box, and the mobile Changes screenYou generate a commit message. The selected files and the branch’s recent commit subjects are filled in, so the subject matches your repo’s existing style.
PR generationThe create-pull-request form in the git view’s PR tabYou generate a PR title and body. Filled with the base and head branches, the commits and changed files between them, your additional context, and the repo’s PR template when one exists.
Merge/rebase conflict resolutionThe conflicts dialog in the git view, when a merge or rebase stops on conflictsYou pick “Resolve in current session” or “Resolve in new session”. The agent reads the conflicted files, proposes a per-file resolution strategy, and waits for your confirmation before editing, staging, or continuing the operation.
Cherry-pick conflict resolutionThe “Re-integrate commits” section for a worktree sessionMoving the session’s commits onto the target branch hits a conflict and you hand it to the agent. The agent resolves inside the temporary worktree, stages the resolved files, and continues the cherry-pick.

GitHub

PromptWhere it runsWhen it fires
PR reviewThe “Link GitHub PR” picker in the composer’s attach menu, and the new worktree dialogTwo triggers. Attaching a PR as context renders the instructions, which go out with your next message. Starting a worktree session from a PR uses the prompt as that session’s opening message, with the full PR context attached.
Issue reviewThe new worktree dialog, when you start the worktree from an issueThe new session’s opening message reviews the issue, with its body and comments attached as context.
PR failed checks / PR comments / single PR comment—Not sent by any flow today. The PR view used to fire these from one-click review actions; failed checks and comments now pin as chat-context drafts instead. They stay editable so existing overrides keep working.

Planning

PromptWhere it runsWhen it fires
Todo planningThe Todos panel in the project sidebarYou send a todo to a session or a new worktree session. The todo text becomes the visible message; the instructions turn it into a question-first planning dialogue instead of jumping straight to implementation.
Improve planThe “Improve” action on a saved plan in the Plans viewYou send a saved plan into an improve flow. The agent reads the plan file first, then proposes changes grounded in the current repo state and offers to edit the same file.
Implement planThe “Implement” action on a saved planYou send a saved plan into an implement flow. The agent reads the plan file and implements it end to end without expanding scope, saving plan adjustments back to the file when the plan itself turns out to be wrong.

Session

Most of these power slash commands typed in the composer. Most also appear as starter chips on a new-session draft.

PromptWhere it runsWhen it fires
Codebase tour/exploreYou ask for a high-level orientation of the codebase.
Session summary/summary, optionally /summary <topic>You summarize the conversation so far, useful for handing off to a new session. Needs an existing session.
Workspace review/workspace-reviewYou ask the agent to review the current workspace diff for intent, correctness, and security.
Feature planning/plan-featureYou turn a rough feature idea into an implementation plan through a guided question-and-answer dialogue.
Goal crafting/craft-goal, optionally /craft-goal <idea>You turn an idea into a verifiable Goal objective for the Goal dialog.
Catch up/catch-upYou return to a project and ask where things stand and what to pick up next.
Debugging/debugYou investigate a bug: the agent forms hypotheses, confirms the root cause from the code, and only then proposes a fix.
Weigh options/weighYou know what you want to build but not how. The agent compares two or three approaches and recommends one.
FusionThe “Run fusion” action on a multi-run groupYou combine the outputs of several runs into one answer. The run outputs are appended after the instructions.

Prompts without a Settings entry

A few prompts fire automatically and have no editable page in Settings:

PromptWhen it fires
Scheduled task/schedule-task, optionally with an initial idea. Guides the dialogue that defines a scheduled task.
Review handoff/handoff-review, or the Review button in the diff view with handoff enabled. Generates the handoff in the working session.
Review session starterThe opening message of the generated review session, with the handoff when one was produced and without it otherwise.
Review feedback / implementation responseShuttle messages between the two sessions: reviewer feedback goes back to the implementing session, and the implementer’s response returns to the review session.