Prompter

English | 简体中文

A prompt workspace for VS Code that turns daily prompt writing into a reusable, trackable workflow.

Compose prompts faster, copy them out with one click, track running work from Claude Code / Codex / Roo Code, and keep prompt history useful after the session ends.

Prompter is built for people who work with AI inside VS Code every day.

Instead of repeatedly copying code selections, file paths, terminal output, and half-finished prompt drafts by hand, Prompter gives you one productized workspace to prepare prompts, organize prompt cards, monitor external sessions, and review what happened later.

It works especially well for workflows built around Claude Code, Codex, Roo Code, Cursor, and any other AI tool that starts with a copied prompt.

Table of Contents

• Why Prompter
• Highlights
• Product Tour
  • Workspace Composer
  • Prompt Status
  • History
  • Shortcuts
  • Settings
• External Session Sync
• Commands and Default Shortcuts
• Storage
• Links

Why Prompter

Prompt work is usually repetitive, fragmented, and easy to lose.

A typical coding workflow often looks like this:

• copy code into an AI chat
• manually add file paths
• paste terminal output by hand
• rebuild the same prompt structure again and again
• forget which prompt is still running
• lose useful prompts once the chat is over

Prompter brings that scattered work back into VS Code and turns it into a repeatable workflow.

Highlights

• Draft first, send later. Write and refine prompts in a dedicated editor before pasting them into an external AI tool.
• Save and copy in one step. Confirming a prompt saves it as a card in Unused and copies it to the clipboard immediately.
• Keep half-finished ideas. Start a new blank draft without losing the current one.
• Track prompt lifecycle visually. Move cards across Unused, In Progress, and Completed, or let imported sessions update automatically.
• Stay connected to external sessions. Detect supported Claude Code, Codex, and Roo Code activity from logs and jump back to the source session.
• Review prompt work like an activity feed. Use a GitHub-style heatmap to revisit what you wrote and used on any day.
• Daily history that stays accurate. At local midnight, Prompter advances the day's progress automatically. You don't have to click anything.
• Deletes that stay deleted. Removed cards are remembered across midnight, restarts, and re-syncs — they don't reappear on their own.
• Adapts to panel width. The status board scales font sizes with the panel's width, so the same view looks right in a narrow side panel and in a wide editor area.

Product Tour

Workspace Composer

The Workspace page is the place where prompt writing starts.

What you can do here:

• write prompts in Markdown inside a dedicated composer
• click Confirm to save the current prompt into Unused and copy it to the clipboard
• click the trash button to clear the current draft when you no longer need it
• click the new-page button to open a blank draft while preserving the current content in Unused
• import editor selections, Explorer resources, and terminal selections into the draft so context gathering stays fast
• drop file paths from the OS file manager onto the composer to attach them as references
• keep prompt preparation inside VS Code instead of scattering it across chats and notes

This page is optimized for the moment before you send a prompt out.

Prompt Status

Below the composer, Prompter shows a dedicated Prompt Status area for prompt cards.

What you can do here:

• view prompts in Board or List mode
• single-click a card to copy it again
• double-click a card to reopen it in the composer for editing
• drag cards across Unused, In Progress, and Completed
• drag a card into the delete zone to remove it quickly
• rename the group name shown on a card; imported prompts are grouped by session, so renaming the group updates that whole session group
• expand long prompt cards when the preview is too short
• jump directly from a card back to the matching Claude Code, Codex, or Roo Code session

Prompter also keeps imported running prompts visible. When a tracked prompt finishes, it can notify you, play a tone, and highlight the card until you acknowledge it.

The status board scales with the panel's width, so lane headings, card titles, and previews stay readable both in a narrow side panel and in a wide editor area — no manual zoom.

History

The History page turns prompt work into something you can actually review.

What you can do here:

• browse prompt activity with a GitHub-style heatmap
• click a specific day to inspect that day's prompts
• view prompts grouped by session so the history is easier to scan
• filter the selected day by Unused, In Progress, or Completed
• expand a prompt preview to read the full content
• copy historical prompts back into use
• inspect associated file references and line ranges for extra context
• watch the day-by-day session-source progress update by itself across midnight — no manual import needed

The day rollover happens automatically: at local midnight Prompter advances the counter for sources whose prompts are already saved, without re-reading any external logs. A manual Start button is still available when you want to force a full re-import.

Shortcuts

The Shortcuts page gives Prompter its own built-in shortcut management UI.

What you can do here:

• review the current shortcut for each Prompter command
• record a new shortcut without editing keybindings.json by hand
• reset any command back to its default binding
• keep the main entry and all import actions easy to trigger from your normal workflow

Today the shortcut page focuses on four core actions:

• opening Prompter
• importing the current editor selection
• importing a selected file or folder from Explorer
• importing the current terminal selection

Settings

The Settings page controls how Prompter behaves in day-to-day use.

What you can configure here:

• interface language (English / 简体中文)
• theme mode (system / light / dark)
• default import path format (absolute or workspace-relative)
• prompt completion notifications and pause notifications
• completion tone, with three built-in choices and an option to use your own audio file
• experimental prompt-pause behavior
• data directory, with a choice to start fresh in the new directory or migrate existing data into it
• log source paths and toggles for Claude Code, Codex, and Roo Code
• a one-click button to clear local cache

The combination lets Prompter fit different operating systems, different log layouts, and different notification preferences.

External Session Sync

Prompter can import prompt activity from external coding-agent logs and keep your status board in sync with what's happening outside the editor.

Supported sources:

• Claude Code
• Codex
• Roo Code

The default log paths follow each tool's native conventions and can be changed in Settings.

Once a log source is enabled and the path is configured, Prompter can:

• detect imported prompts from those sessions
• group them by session
• keep running prompts visible in the workspace
• mark prompts as completed when the source session finishes
• highlight freshly completed prompts until you acknowledge them
• open the matching external session again from the prompt card
• update per-day session-source progress automatically at local midnight

This is what makes Prompter more than a local scratchpad. It becomes a control surface for prompts that continue running outside the editor.

When you delete an imported prompt card, the deletion is remembered persistently — that prompt stays gone across day rollovers, restarts, and future re-imports.

Commands and Default Shortcuts

Notes:

• The three import commands intentionally share the same default shortcut because each one is gated by a different when clause in VS Code, so they don't conflict.
• Prompter: Import Selection to Prompt is also available from the editor right-click menu when text is selected.
• Prompter: Add Resource to Prompt appears in the file Explorer right-click menu.
• Prompter: Import Terminal Selection appears in the terminal right-click menu.
• Prompter also adds an Activity Bar entry so the workspace stays easy to reopen.

Storage

By default, Prompter stores all data under ~/.prompter in your home directory.

The data directory holds:

• your settings
• saved prompt cards, organized by day
• reusable prompt snippets
• session group names and history-import progress

You can move the data directory at any time from Settings, with a choice between starting fresh and migrating existing data into the new location.

If local data ever gets damaged (for example after a force-quit), the Prompter: Recover Corrupted Data command will scan the on-disk backups and restore what it can.

Links

• GitHub: https://github.com/hzxwonder/Prompter
• Chinese README: README.zh-CN.md
• License: LICENSE.md