Import, Export, and Reset Operations
PostQode provides dedicated mechanisms to export execution records, import custom agent modes and workspace rules, and safely reset corrupted state through built-in debug utilities.
1. Exporting Task History
PostQode allows you to export complete task execution trajectories—including user prompts, model reasoning chains, tool invocations, terminal outputs, and token/cost metrics.
Exact Location in the UI
PostQode Panel ➔ Task History (Top Header) ➔ Hover Over Task ➔ Click "EXPORT" (Top-Right)
- Open the PostQode Panel in the VS Code sidebar.
- Click the Task History icon () in the top navigation bar.
- Locate the specific task in the history list (you can filter by current workspace or search by keyword).
- Hover over the task card: An EXPORT button will appear in the top-right corner of the card.
- Click EXPORT to download the complete task record to your local system.
What is Included in an Exported Task
- Full Prompt Trajectory: All user instructions, clarifications, and agent responses.
- Tool Invocations & Diffs: Detailed records of files read, surgical patches applied, and terminal commands executed.
- Thinking / Reasoning Tokens: Chain-of-thought steps captured from reasoning models (e.g. DeepSeek R1, Claude 3.7 Sonnet Thinking, o3-mini).
- Execution Telemetry: Exact prompt tokens, completion tokens, cache read tokens, latency, and estimated cost breakdown.
Common Use Cases
- Bug Reports & Team Collaboration: Share reproducible execution traces with teammates without giving direct repository access.
- Prompt Engineering Archiving: Save effective planning or refactoring prompt sequences for future reference.
- Audit Compliance: Retain structured execution logs for security and architectural reviews.
2. Importing Rules, Workflows, and Custom Modes
To maintain maximum security, PostQode avoids monolithic settings export files that risk exposing plaintext API keys. Instead, configuration and rule imports are handled through modular, version-controlled formats:
Importing Custom Rules (.postqode/rules/)
- Project-Specific Rules: Add Markdown files directly into
.postqode/rules/in your repository root (e.g.,.postqode/rules/coding-standards.md). PostQode automatically ingests and applies these rules across all task sessions in that workspace. - Global User Rules: Place rules in
~/.postqode/rules/to enforce personal guidelines across all projects on your machine.
Importing Reusable Workflows (.postqode/workflows/)
- Save multi-step automated sequences in
.postqode/workflows/as.mdfiles. - Trigger them anytime in chat using
/workflow <workflow-name>or/globalworkflow <workflow-name>.
Importing Custom Agent Modes (YAML)
- Open the Prompts Tab () from the top navigation bar.
- Under the Modes section, click the Import Mode button.
- Select your
.yamlmode definition file. PostQode validates the role definition, allowed tool groups, and system prompt schema, making the new agent immediately available in the mode selector.
Enterprise Web Console Sync
- Organizations using Web Rules Management can author and verify rules in the Web Console. Connected IDE extensions sync verified rules automatically without manual file transfers.
3. Resetting State (Debug Settings)
When troubleshooting context desynchronization, stuck background processes, or credential issues, PostQode provides targeted reset actions located in the Debug settings panel.
Exact Location in the UI
PostQode Settings (Gear Icon) ➔ Debug Tab ➔ Danger Zone
- Open PostQode settings by clicking the gear icon () in the top-right corner of the PostQode panel.
- In the settings navigation sidebar, select the Debug tab.
- Locate the Danger Zone buttons:
Reset Options Compared
| Action | Scope | What Gets Reset | When to Use |
|---|---|---|---|
| Reset Workspace State | Active Project | Clears project-level session cache, active task context, and temporary scratch buffers (.postqode/scratch/). | • Task context gets stuck or unresponsive. • Checkpoints cache becomes out of sync with git. • Source code is never touched or modified. |
| Reset Global State | Entire Extension | Completely resets all extension preferences, clears VS Code Secret Storage (API keys and auth tokens), and removes all cached global state. | • Performing a clean-slate re-installation. • Switching primary enterprise organization accounts. • Resolving persistent authentication lockouts. |
Secret Storage Notice
Clicking Reset Global State will clear your stored API keys and cached credentials from VS Code Secret Storage. Ensure you have your API keys or PostQode login credentials handy before performing a global reset.
4. PostQode Settings Navigation Quick Reference
PostQode settings are organized into 8 specialized tabs:
| Tab ID | Tab Name | Description |
|---|---|---|
api-config | Model Configuration | Dual Mode setup (Plan vs Agent models), provider selection, API keys, and temperature sliders. |
browser | Browser Settings | Web Agent controls (Headless mode, vision mode, persistent sessions, and proxies). |
agents | Agent Management | Toggle and configure specialized built-in agents (code-reviewer, doc-writer, web-qa, etc.). |
features | Feature Settings | Focus Chain reminder intervals, context scratchpads (.postqode/scratch/), and checkpoints. |
terminal | Terminal Settings | Shell profile overrides, command auto-approval, and output buffer limits. |
preRequisites | Pre-requisites | Environment readiness check for Mobile Agent (Android adb, Appium, Node.js, Java JDK). |
debug | Debug Tools | Reset Workspace State, Reset Global State, and announcement reset triggers. |
about | About PostQode | Extension version, daemon connection status, and changelog. |