Files
Reactive-Resume/docs/guides/managing-resumes-from-the-dashboard.mdx
T
Amruth Pillai 6d8d8f6e55 feat: add AI agent workspace (#3062)
* 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
2026-05-14 15:00:04 +02:00

114 lines
3.5 KiB
Plaintext

---
title: "Managing resumes from the dashboard"
description: "Learn how to sort, filter, open, duplicate, lock, update, and delete resumes from the Resumes dashboard."
---
The **Resumes** dashboard is where you manage every resume in your account. Use it to keep separate versions for different roles, clients, locations, or application stages.
<Frame caption="Resumes dashboard in grid view">
<img
src="/images/guides/managing-resumes-from-the-dashboard/screenshot-1.webp"
alt="Resumes dashboard showing sort controls, grid view, create and import cards, and a sample resume"
/>
</Frame>
## Choose a view
The dashboard supports two views:
- **Grid** shows each resume as a card. This is useful when you want a visual overview.
- **List** shows resumes in rows. This is useful when you have many resumes and want a denser view.
Use the **Grid** and **List** tabs in the top-right of the dashboard to switch between them.
<Frame caption="Resumes dashboard in list view">
<img
src="/images/guides/managing-resumes-from-the-dashboard/screenshot-2.webp"
alt="Resumes dashboard showing the same resume in list view"
/>
</Frame>
## Sort resumes
Use the **Sort by** menu to change the order of your resumes.
| Sort option | When to use it |
| --- | --- |
| **Last Updated** | Find the resume you worked on most recently. |
| **Created** | Review resumes by when they were first created. |
| **Name** | Keep resumes in alphabetical order. |
## Filter by tags
If you add tags to your resumes, the dashboard shows a **Filter by** menu. Select one or more tags to show only matching resumes.
Tags are useful for grouping resumes by:
- target role, such as `frontend` or `product`;
- application status, such as `draft` or `sent`;
- market, region, client, or company name.
<Tip>
You can add or change tags when creating, updating, or duplicating a resume.
</Tip>
## Open a resume
Click a resume card or row to open it in the builder.
You can also open the resume menu and choose **Open**.
## Update name, slug, and tags
Use **Update** when you want to change a resume's metadata.
<Steps>
<Step title="Open the resume menu">
On the dashboard, open the menu for the resume you want to edit.
</Step>
<Step title="Choose Update">
Select **Update** to open the resume details dialog.
</Step>
<Step title="Edit the fields">
Change the **Name**, **Slug**, or **Tags**.
</Step>
<Step title="Save changes">
Click **Save Changes**.
</Step>
</Steps>
<Warning>
The slug is part of the public URL. If a resume is public, changing the slug changes the link people use to view it.
</Warning>
## Duplicate a resume
Use **Duplicate** when you want to create a new version without changing the original.
The duplicate dialog starts with the same tags, a copied name, and a copied slug. Edit these before saving if you want the new version to be easier to identify.
Good reasons to duplicate a resume:
- tailoring one resume for a specific job posting;
- keeping a short and long version;
- testing a new template or layout;
- creating a localized version.
## Lock or unlock a resume
Use **Lock** to prevent accidental edits or deletion. A locked resume cannot be updated or deleted until you unlock it.
To edit a locked resume later, open the resume menu and choose **Unlock**.
## Delete a resume
Use **Delete** only when you no longer need the resume.
<Warning>
Deleting a resume cannot be undone. If you might need the content later, export a JSON backup first. See
[Exporting your resume](/guides/exporting-your-resume).
</Warning>