Skip to content
Back to search

chat-outline

MarketplaceWorks with Claude CodeGitHub

The chat-outline mod: an outline pane listing each prompt of the conversation

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/conradstack--chat-outline/badge.svg)](/listings/conradstack--chat-outline)

HTML

<a href="/listings/conradstack--chat-outline"><img src="/api/listings/conradstack--chat-outline/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

At the prompt of a Claude Code terminal session:

/plugin install chat-outline --marketplace ConradStack/chat-outline

Or from a shell:

claude plugin install chat-outline --marketplace ConradStack/chat-outline

Answer `y` to add the marketplace, then pick a scope (the user scope loads the mod in every session you start after).

In the Claude desktop app, where `/plugin` does not run: click + next to the prompt box, then Plugins, Add marketplace with `ConradStack/chat-outline`, then Add plugin. A mod installed from a terminal at the user scope also loads in the desktop app's local sessions.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 6 lines
  1. {
  2. "name": "chat-outline",
  3. "description": "The chat-outline mod: an outline pane listing each prompt of the conversation",
  4. "owner": { "name": "ConradStack" },
  5. "plugins": [{ "name": "chat-outline", "source": "./" }]
  6. }
README.md · README · 174 lines
  1. # chat-outline
  2. A Claude Code mod that adds an **Outline** pane beside the chat. The pane
  3. lists every prompt you have sent in the current conversation, so you can see
  4. the shape of a long session at a glance.
  5. Each prompt in the outline shows:
  6. - its number (`#1`, `#2`, ...), in bold
  7. - the time you sent it, in your local time; the date is added for prompts
  8. not sent today (`2026-11-18 17:25`)
  9. - the full text of the prompt, wrapped across lines, cut off with `...` past
  10. a character limit (1000 by default)
  11. A dashed rule separates one prompt from the next. The pane updates as you
  12. send new prompts and empties after `/clear`.
  13. Only your own prompts are listed. Claude's replies, tool results, slash
  14. command records, background task notifications and system reminders are left
  15. out.
  16. ## Installing
  17. At the prompt of a Claude Code terminal session:
  18. ```
  19. /plugin install chat-outline --marketplace ConradStack/chat-outline
  20. ```
  21. Or from a shell:
  22. ```bash
  23. claude plugin install chat-outline --marketplace ConradStack/chat-outline
  24. ```
  25. Answer `y` to add the marketplace, then pick a scope (the user scope loads
  26. the mod in every session you start after).
  27. In the Claude desktop app, where `/plugin` does not run: click + next to the
  28. prompt box, then Plugins, Add marketplace with `ConradStack/chat-outline`,
  29. then Add plugin. A mod installed from a terminal at the user scope also loads
  30. in the desktop app's local sessions.
  31. ## Updating
  32. To get the latest version of an installed copy, from a shell:
  33. ```bash
  34. claude plugin update chat-outline@chat-outline
  35. ```
  36. Then restart Claude Code to load the new version. Your settings are kept.
  37. ## Loading from a local folder
  38. To run the mod from a checkout of this repository instead, for example while
  39. changing it, load the folder with either of these.
  40. For a single terminal session:
  41. ```bash
  42. claude --plugin-dir /path/to/chat-outline
  43. ```
  44. For sessions you cannot pass a flag to, such as those the Claude desktop app
  45. starts, name the folder in `CLAUDE_CODE_PLUGIN_DIRS`, in the process
  46. environment or in the `env` block of `~/.claude/settings.json`:
  47. ```json
  48. {
  49. "env": {
  50. "CLAUDE_CODE_PLUGIN_DIRS": "/path/to/chat-outline"
  51. }
  52. }
  53. ```
  54. Several folders are separated by the platform's path-list separator (`:` on
  55. macOS and Linux).
  56. ## Using it
  57. The Outline pane opens when a session starts, unless you turn `autoOpen`
  58. off (see Settings). If you close it, or it was not opened, type `/outline`
  59. to open it.
  60. ## Settings
  61. | Option | Type | Default | What it does |
  62. | --- | --- | --- | --- |
  63. | `maxQueryChars` | whole number, 1 or more | 1000 | Prompts longer than this are cut off in the outline |
  64. | `autoOpen` | `true` or `false` | `true` | Whether the pane opens when a session starts; when `false`, run `/outline` to open it |
  65. Leaving an option unset is fine: the outline then uses its default. To
  66. change one, pick one of these:
  67. - At the prompt of a terminal session:
  68. ```
  69. /plugin configure chat-outline@chat-outline
  70. ```
  71. - When installing, pass the value with `--config`:
  72. ```bash
  73. claude plugin install chat-outline --marketplace ConradStack/chat-outline --config maxQueryChars=500
  74. ```
  75. - Edit `~/.claude/settings.json`. An installed copy is keyed by its plugin id,
  76. `chat-outline@chat-outline`:
  77. ```json
  78. {
  79. "pluginConfigs": {
  80. "chat-outline@chat-outline": {
  81. "options": { "maxQueryChars": 500, "autoOpen": false }
  82. }
  83. }
  84. }
  85. ```
  86. A copy loaded from a local folder with `--plugin-dir` or
  87. `CLAUDE_CODE_PLUGIN_DIRS` is not installed, and may be keyed as
  88. `chat-outline@inline` instead. If an option holds a value of the wrong kind,
  89. the pane shows an error instead of the outline (and opens at session start
  90. so the error is seen).
  91. ## Limitations
  92. - **No click-to-scroll in the desktop app.** The outline is read-only. The
  93. desktop app refuses to let a mod scroll its conversation, so clicking a
  94. prompt cannot jump to it there.
  95. - **Timestamps come from the session's transcript file.** The mod reads the
  96. file's new lines each time the pane is drawn. If the file cannot be read,
  97. a dim note at the top of the pane says why, and the prompts are listed
  98. without times.
  99. - **Which prompts count is a heuristic.** A user message whose text starts
  100. with `<` is treated as engine-made (a slash command record or a reminder)
  101. and left out, so a prompt you typed that starts with `<` is left out too.
  102. ## Files
  103. - `.claude-plugin/plugin.json` - the manifest, including the `maxQueryChars`
  104. and `autoOpen` options
  105. - `.claude-plugin/marketplace.json` - makes this repository a marketplace
  106. listing the mod, so it installs with one line
  107. - `hooks/hooks.json` - names the hooks module
  108. - `hooks/register.tsx` - the mod: the pane, the `/outline` command, and the
  109. hooks that refresh the pane
  110. - `hooks/register.test.tsx` - tests
  111. - `types/index.d.ts` - the type contract for the mod's one stored value
  112. Claude Code writes `.claude-plugin/types/` each time it loads the mod. It is
  113. generated, so it is left out of git.
  114. ## Development
  115. Check the manifest and module the way Claude Code will load them:
  116. ```bash
  117. claude plugin validate .
  118. ```
  119. Run the tests:
  120. ```bash
  121. claude plugin test .
  122. ```
  123. Type-check, once Claude Code has loaded the mod and written
  124. `.claude-plugin/types/`:
  125. ```bash
  126. npx -p typescript tsc -p .
  127. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.