mirror of
https://github.com/AmruthPillai/Reactive-Resume.git
synced 2026-07-14 06:47:00 +10:00
Amruth Pillai
6d8d8f6e55
* chore(ai): remove local AI store now that providers live server-side
The Zustand-based useAIStore has been replaced by the server-side
aiProviders oRPC router (encrypted credentials persisted in DB).
Delete the dead store + tests, drop the ./store export, and remove
zustand/immer deps which are no longer referenced anywhere in
packages/ai/src/.
* feat(agent): archive/delete actions and read-only state for agent threads
- Backend: mark archived threads as read-only in threads.get and reject
messages.send with CONFLICT when the thread is archived.
- Frontend: render archived threads in the sidebar with muted styling and
an Archived badge; add a per-thread dropdown menu in the chat header
with Archive (non-destructive) and Delete (with confirmation); show a
read-only banner above the message list that disambiguates archived
vs. missing-resource causes; suppress the Retry and Stop buttons in
read-only mode.
- Tests: new packages/api/src/services/agent.test.ts covering the
archived-thread isReadOnly flag and the archived-thread send refusal.
* fix(agent): abort run on archive and verify ownership before deleting thread
- threads.archive: before flipping status, abort any in-flight run controller
and clear the active-run state on the thread; cleanup failures are logged
but do not block the status update.
- threads.delete: assert thread ownership via getThread before destructive
work so an authenticated user cannot wipe another user's attachment rows
by passing a foreign threadId.
Adds focused tests for both behaviors.
* feat(agent): display patch diffs and surface revert conflicts
Render apply_resume_patch tool messages with a status-aware card (applied/
reverted/conflicted), expandable operation list, and a Revert button that
correctly handles RESUME_VERSION_CONFLICT responses. Adds unit tests for
the inverse-patch builder and the agentService.actions.revert flow.
* chore(agent): remove out-of-scope attachment tests accidentally added in Task 6
The Task 6 commit (73ef1acca) accidentally re-introduced three attachment-
related tests that belong to a separate task:
- `buildAttachmentModelParts > converts text, image, supported binary, and
unsupported attachments into model parts`
- `agentService.messages.send > persists the user message with file UI parts
and links selected attachments to it` (was failing — the `ToolLoopAgent`
mock is not callable as a constructor)
- `agentService.messages.send > rejects attachments that are missing, foreign,
or already linked before persisting a message`
These were likely re-added during a stash recovery and were not requested
for Task 6, whose scope was limited to the `agentService.actions.revert`
flow. Remove them along with the helpers/fixtures (`buildAttachment`,
`buildActiveThread`, `selectWhereResult`, `selectOrderByResult`) that they
were the only consumers of. `selectLimitResult` is preserved because it is
used by the revert tests.
* chore(agent): configure runtime dependencies
* feat(db): add agent workspace schema
* feat(api): add agent backend services
* feat(web): add agent workspace UI
* chore(agent): remove legacy builder assistant
* test(agent): make agent stream mocks constructible
* chore(web): remove unused resume replacement hook
* feat(api): add unsafe AI base URL flag
* chore(dev): expose local services in compose
* fix(web): normalize resume preview gaps
* feat(api): improve agent tool handling
* feat(web): polish agent workspace UI
* chore: update dependencies
* fix(api,web): address PR review feedback for agent workspace
Security/correctness:
- Restrict AI provider URLs to http/https even in unsafe mode
- Stop exposing Redis on host network by default
- Make .env.local optional and drop app profile in compose.dev.yml
- Store agent attachments with private ACL on S3
- Reset provider test status when provider/model/baseURL changes
- Decouple non-agent AI endpoints from REDIS_URL requirement
- Fix JSON Patch add inverse for existing object members
- Wrap resume patch + agent action insert in db transaction
- Validate partialMessage at runtime and rate-limit attachment uploads
- Add unique index on agent_messages (thread_id, sequence)
UX/bugs:
- Mark agent thread route as ssr: false and guard SSE chunk parsing
- Show config-specific banner only on known configuration error
- Gate AI provider checks behind loading state in resume import
- Fix relative-time formatter blank gap between 45-59 seconds
- Clarify thread delete confirmation message
Polish:
- Raise ENCRYPTION_SECRET minimum to 32 characters
- Bucket AI rate limits by resumeId/threadId/messageId
- Trim form values before submitting AI provider config
- Use single key identifier and nullish-coalesce baseURL display
* fix: address ai agent review feedback
* fix: preserve mobile agent chat state
* docs: add ai agent workspace guides
* feat: introduce design system for Reactive Resume
81 lines
3.3 KiB
Plaintext
81 lines
3.3 KiB
Plaintext
---
|
|
title: "Importing resumes"
|
|
description: "Learn which file formats Reactive Resume can import and how to import an existing resume from the dashboard."
|
|
---
|
|
|
|
Reactive Resume can create a new resume from several existing file formats. Use import when you are moving from another tool, restoring a backup, or converting an older Reactive Resume file.
|
|
|
|
## Supported import formats
|
|
|
|
| Format | Requires AI integration? | Notes |
|
|
| --- | --- | --- |
|
|
| **Reactive Resume (JSON)** | No | Best option for backups exported from the current version of Reactive Resume. |
|
|
| **Reactive Resume v4 (JSON)** | No | Use this for files exported from Reactive Resume v4. |
|
|
| **JSON Resume** | No | Use this for files that follow the JSON Resume schema. |
|
|
| **PDF** | Yes | Reactive Resume asks your configured AI provider to parse the file into structured resume data. |
|
|
| **Microsoft Word** | Yes | Supports Word documents. Reactive Resume asks your configured AI provider to parse the document. |
|
|
|
|
<Info>
|
|
PDF and Word imports depend on your AI settings because those formats are not structured resume data. Configure AI in
|
|
**Dashboard -> Settings -> Integrations** before using those import types.
|
|
</Info>
|
|
|
|
## Import a resume
|
|
|
|
<Steps>
|
|
<Step title="Open the Resumes dashboard">
|
|
Sign in and go to **Dashboard -> Resumes**.
|
|
</Step>
|
|
|
|
<Step title="Click Import an existing resume">
|
|
Select the **Import an existing resume** card.
|
|
|
|
<Frame caption="Import an existing resume dialog">
|
|
<img
|
|
src="/images/guides/importing-resumes/screenshot-1.webp"
|
|
alt="Import dialog showing supported resume import types"
|
|
/>
|
|
</Frame>
|
|
</Step>
|
|
|
|
<Step title="Choose the import type">
|
|
Pick the format that matches your file.
|
|
</Step>
|
|
|
|
<Step title="Select the file">
|
|
Click the file selector and choose the resume file from your computer.
|
|
</Step>
|
|
|
|
<Step title="Import">
|
|
Click **Import**. Reactive Resume creates a new resume and opens it in the builder when the import succeeds.
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Choose the right import type
|
|
|
|
If you have a file exported from Reactive Resume, choose **Reactive Resume (JSON)**. This preserves the most information because the file already matches Reactive Resume's data model.
|
|
|
|
If you are coming from Reactive Resume v4, choose **Reactive Resume v4 (JSON)**.
|
|
|
|
If your file is a standard JSON Resume document, choose **JSON Resume**.
|
|
|
|
If you only have a PDF or Word document, choose **PDF** or **Microsoft Word**. After import, review every section carefully. AI parsing can save time, but it can also miss details, change wording, or place content in the wrong section.
|
|
|
|
<Warning>
|
|
Always review an imported resume before sharing or exporting it. This is especially important for PDF and Word imports.
|
|
</Warning>
|
|
|
|
## Troubleshooting
|
|
|
|
### The PDF or Word import says AI must be enabled
|
|
|
|
Open **Dashboard -> Settings -> Integrations**, fill in your AI provider settings, test the connection, and enable AI features.
|
|
|
|
### The imported resume is incomplete
|
|
|
|
Try importing a cleaner source file. Simple resumes with selectable text import more reliably than scanned documents, image-heavy PDFs, or files with complex tables.
|
|
|
|
### The JSON file is rejected
|
|
|
|
Make sure you selected the correct JSON import type. A Reactive Resume JSON export, a Reactive Resume v4 JSON export, and a JSON Resume file are different formats.
|