RevampKeyRevampKey home
Menu
Guide

Frequently asked questions

Quick answers about files, projects, context, planning, MCP Servers, delegated work, and help.

What is RevampKey?

RevampKey is a desktop app for existing projects and repositories. Describe a change, provide relevant context, and review the work as it progresses. Start with How RevampKey works.

What is the difference between the Files pane and Code Structure?

The Files pane is for browsing, searching, previewing, and adding specific workspace items. Code Structure settings control optional structural context separately for main and delegated work. Read Files and workspaces and Codebase Structure.

How are Projects, conversations, and Chats different?

Projects keep related repository work together. Conversations can be nested under a project, while standalone Chats live in their own area. A child conversation is not duplicated in the standalone list. Read Projects, conversations, and tasks.

Can one workspace contain multiple folders or repositories?

Yes. Use the smallest set that the change genuinely needs, keep root boundaries explicit, and state which repository owns the behavior. See Files and workspaces.

Are images and PDFs supported?

Yes. Up to 5 attachments can be added at once, each image can be up to 5 MB, and each PDF can be up to 25 MB. PDFs do not provide an image preview in the attachment list. See Context and attachments.

Will a task always include a plan?

No. Planning adapts to the request. A small local fix may stay direct, while broader work may include plans, modules, or other review artifacts. See Plans and modules.

What are Past Work Reports?

They are earlier task reports that can be reused as visible context when they are relevant. Current defaults keep them hidden from main work and show them to delegated work. There is no separate report-library browser. Read Past Work Reports.

What does delegated work show?

RevampKey may delegate a focused part of a task and show pending, completed, failed, abandoned, or session-ended states. Expand visible task, numbered-step, approval, and file-change details before deciding what to do next. See Delegated work.

What are MCP Servers?

MCP Servers are optional tool connections. The catalog has 14 built-in connectors: three without an additional credential, four using an API key, token, or connection input, six using browser sign-in, and GitHub using device-code sign-in. Read MCP Servers for the display names and states.

Can I add a custom MCP server?

Yes. The visible form supports Local (stdio) with a command, space-separated arguments, and optional KEY=VALUE environment lines, or Remote (HTTP/SSE) with a URL. Review the trusted local-command warning before enabling it.

Does RevampKey create a commit for every task?

No commit is promised for every task. Review the resulting files and your project's Git state in Changes and verification.

Where can I get help?

Start with Troubleshooting, then use the support actions below if the visible task details do not resolve the issue. For billing or plan questions, review Billing and usage.

Still have a question?

Report a documentation problem or contact the RevampKey team.