mirror of
https://github.com/AmruthPillai/Reactive-Resume.git
synced 2026-06-22 04:11:55 +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
97 lines
3.3 KiB
Plaintext
97 lines
3.3 KiB
Plaintext
---
|
|
title: "Exporting your resume"
|
|
description: "Learn how to export your resume as PDF, DOCX, or JSON from the builder."
|
|
---
|
|
|
|
Reactive Resume can export your resume in three formats:
|
|
|
|
| Format | Best for |
|
|
| --- | --- |
|
|
| **PDF** | Job applications, recruiter emails, printing, and public resume downloads. |
|
|
| **DOCX** | Further editing in Microsoft Word, Google Docs, or another word processor. |
|
|
| **JSON** | Backups, restoring a resume later, importing into another Reactive Resume account, or sharing structured data with an AI assistant. |
|
|
|
|
## Export from the right sidebar
|
|
|
|
<Steps>
|
|
<Step title="Open your resume in the builder">
|
|
Go to the dashboard and open the resume you want to export.
|
|
</Step>
|
|
|
|
<Step title="Open the Export section">
|
|
In the right sidebar, select **Export**.
|
|
|
|
<Frame caption="Export section in the resume builder">
|
|
<img
|
|
src="/images/guides/exporting-your-resume/screenshot-1.webp"
|
|
alt="Export section showing JSON, DOCX, and PDF download buttons"
|
|
/>
|
|
</Frame>
|
|
</Step>
|
|
|
|
<Step title="Choose a format">
|
|
Click **JSON**, **DOCX**, or **PDF**.
|
|
</Step>
|
|
|
|
<Step title="Save the file">
|
|
Your browser downloads the exported file using the resume name as the filename.
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Export from the builder dock
|
|
|
|
The floating dock at the bottom of the builder also includes quick download buttons for **JSON**, **DOCX**, and **PDF**.
|
|
|
|
Use the dock when you already know which format you need. Use the right sidebar's **Export** section when you want the format descriptions next to each button.
|
|
|
|
For more dock controls, see [Using the builder dock](/guides/using-the-builder-dock).
|
|
|
|
## Export as PDF
|
|
|
|
Choose **PDF** when you need a file that preserves your resume layout.
|
|
|
|
Use PDF for:
|
|
|
|
- uploading to job applications;
|
|
- emailing recruiters or hiring managers;
|
|
- printing;
|
|
- sharing a finished copy outside Reactive Resume.
|
|
|
|
<Info>
|
|
The PDF is generated from your current resume data, template, typography, design, layout, and page settings.
|
|
</Info>
|
|
|
|
## Export as DOCX
|
|
|
|
Choose **DOCX** when you want to continue editing your resume in a word processor.
|
|
|
|
Use DOCX for:
|
|
|
|
- making final manual edits in Microsoft Word;
|
|
- collaborating with someone who prefers Word or Google Docs;
|
|
- submitting to a system that requires a Word document.
|
|
|
|
<Warning>
|
|
DOCX exports are useful for editing, but the visual layout may not match the PDF exactly. Use PDF when exact visual
|
|
fidelity matters.
|
|
</Warning>
|
|
|
|
## Export as JSON
|
|
|
|
Choose **JSON** when you want a structured backup of your resume.
|
|
|
|
The JSON export includes your resume content and settings. You can import it later from the dashboard to restore the resume or create another version.
|
|
|
|
JSON is also useful when working with AI assistants. You can export JSON, ask an assistant to review or edit the structured data, then import the revised JSON as a new resume.
|
|
|
|
<Warning>
|
|
Review AI-generated changes before importing or using them. AI assistants can make mistakes or add details that do not
|
|
reflect your experience.
|
|
</Warning>
|
|
|
|
## Public resume downloads
|
|
|
|
If your resume is public, visitors can download a PDF from the public resume page. You can enable public access in the builder's **Sharing** section.
|
|
|
|
For the full public sharing workflow, see [Sharing your resume publicly](/guides/sharing-your-resume-publicly).
|