diff --git a/docs/api/index.md b/docs/api/index.md
index 9ed2407..96411ce 100644
--- a/docs/api/index.md
+++ b/docs/api/index.md
@@ -78,6 +78,8 @@ BitLogger API navigation.
 - [default-style-tag-registry.md](./default-style-tag-registry.md)
 - [text-formatter-type.md](./text-formatter-type.md)
 - [text-formatter.md](./text-formatter.md)
+- [text-formatter-with-style-markup.md](./text-formatter-with-style-markup.md)
+- [text-formatter-without-style-markup.md](./text-formatter-without-style-markup.md)
 - [format-text.md](./format-text.md)
 - [format-json.md](./format-json.md)
 - [text-formatter-config.md](./text-formatter-config.md)
diff --git a/docs/api/text-formatter-with-style-markup.md b/docs/api/text-formatter-with-style-markup.md
new file mode 100644
index 0000000..a3d825f
--- /dev/null
+++ b/docs/api/text-formatter-with-style-markup.md
@@ -0,0 +1,78 @@
+---
+name: text-formatter-with-style-markup
+group: api
+category: formatter
+update-time: 20260613
+description: Return a TextFormatter with a different message style-markup policy.
+key-word:
+    - formatter
+    - style
+    - markup
+    - public
+---
+
+## Text-formatter-with-style-markup
+
+Return a copy of a `TextFormatter` with a different message-text style-markup policy. This method is the focused way to change how inline tags inside the main log message are interpreted while preserving the rest of the formatter configuration.
+
+### Interface
+
+```moonbit
+pub fn TextFormatter::with_style_markup(self : TextFormatter, style_markup : StyleMarkupMode) -> TextFormatter {
+```
+
+#### input
+
+- `self : TextFormatter` - Base formatter to copy.
+- `style_markup : StyleMarkupMode` - New message-text markup policy.
+
+#### output
+
+- `TextFormatter` - A new formatter value carrying the updated message markup setting.
+
+### Explanation
+
+Detailed rules explaining key parameters and behaviors
+
+- This method only changes `style_markup`, which controls the main message text.
+- The returned formatter preserves timestamp, level, target, field, template, color, and registry settings from `self`.
+- Target and field-value markup settings remain unchanged because they have separate dedicated scopes.
+- The original formatter value is not mutated.
+
+### How to Use
+
+Here are some specific examples provided.
+
+#### When Need To Restrict Message Tags To Built-ins
+
+When messages should allow built-in tags but not custom registry-driven tags:
+```moonbit
+let formatter = text_formatter(color_mode=ColorMode::Always)
+  .with_style_markup(StyleMarkupMode::Builtin)
+```
+
+In this example, message rendering switches to built-in-only tag resolution while the rest of the formatter stays the same.
+
+#### When Need To Reuse One Formatter With Different Message Policies
+
+When a shared base formatter should produce one literal and one styled variant:
+```moonbit
+let base = text_formatter(color_mode=ColorMode::Always)
+let literal = base.with_style_markup(StyleMarkupMode::Disabled)
+let rich = base.with_style_markup(StyleMarkupMode::Full)
+```
+
+In this example, both derived formatters keep the same non-markup configuration.
+
+### Error Case
+
+e.g.:
+- There is no separate failure path for valid `TextFormatter` and `StyleMarkupMode` values.
+
+- If callers need to change target or field markup behavior too, they must use the corresponding dedicated formatter methods instead of assuming this changes every scope.
+
+### Notes
+
+1. This method only affects the main message text, not target text or field values.
+
+2. `without_style_markup()` is the convenience form for the common disabled case.
diff --git a/docs/api/text-formatter-without-style-markup.md b/docs/api/text-formatter-without-style-markup.md
new file mode 100644
index 0000000..1f107f6
--- /dev/null
+++ b/docs/api/text-formatter-without-style-markup.md
@@ -0,0 +1,76 @@
+---
+name: text-formatter-without-style-markup
+group: api
+category: formatter
+update-time: 20260613
+description: Return a TextFormatter with message style markup disabled.
+key-word:
+    - formatter
+    - style
+    - disable
+    - public
+---
+
+## Text-formatter-without-style-markup
+
+Return a copy of a `TextFormatter` with message style markup disabled. This is the convenience helper for the common case where message text should stay literal even if it contains tag-like syntax.
+
+### Interface
+
+```moonbit
+pub fn TextFormatter::without_style_markup(self : TextFormatter) -> TextFormatter {
+```
+
+#### input
+
+- `self : TextFormatter` - Base formatter to copy.
+
+#### output
+
+- `TextFormatter` - A new formatter value whose message markup policy is `StyleMarkupMode::Disabled`.
+
+### Explanation
+
+Detailed rules explaining key parameters and behaviors
+
+- This method is a convenience wrapper over `with_style_markup(StyleMarkupMode::Disabled)`.
+- Only the message-text markup scope changes.
+- Target and field-value markup settings are preserved as-is.
+- The original formatter value is not mutated.
+
+### How to Use
+
+Here are some specific examples provided.
+
+#### When Need Literal Message Text
+
+When log messages may contain `<tag>`-like text that should not be parsed:
+```moonbit
+let formatter = text_formatter(color_mode=ColorMode::Always)
+  .without_style_markup()
+```
+
+In this example, message text is rendered literally instead of interpreting inline style tags.
+
+#### When Need A Safe Variant Of A Styled Base Formatter
+
+When one formatter should keep the same colors and template but stop parsing message tags:
+```moonbit
+let base = text_formatter(color_mode=ColorMode::Always)
+let safe = base.without_style_markup()
+```
+
+In this example, the derived formatter only changes the message markup policy.
+
+### Error Case
+
+e.g.:
+- There is no dedicated failure path for valid `TextFormatter` values.
+
+- If target or field scopes should also stop parsing tags, callers need the corresponding dedicated formatter methods rather than this message-only helper.
+
+### Notes
+
+1. Use this helper when the disabled case is what you want directly.
+
+2. It is equivalent to calling `with_style_markup(StyleMarkupMode::Disabled)` explicitly.