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
95 lines
3.6 KiB
Plaintext
95 lines
3.6 KiB
Plaintext
---
|
|
title: "Using Artificial Intelligence"
|
|
description: "Learn how to configure an AI provider for AI-assisted features in Reactive Resume."
|
|
---
|
|
|
|
Reactive Resume uses AI providers for features such as resume analysis, AI-assisted resume changes, AI agent drafts, and PDF or Word imports.
|
|
|
|
## Open AI provider settings
|
|
|
|
<Steps>
|
|
<Step title="Sign in to the dashboard">
|
|
Head over to [https://rxresu.me](https://rxresu.me) and sign in with your account credentials.
|
|
</Step>
|
|
|
|
<Step title="Navigate to Integrations settings">
|
|
In the dashboard sidebar, under **Settings**, click **Integrations**.
|
|
|
|
<Frame caption="AI provider settings in Integrations">
|
|
<img
|
|
src="/images/guides/using-ai/screenshot-1.webp"
|
|
alt="Integrations settings showing AI provider configuration"
|
|
/>
|
|
</Frame>
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Add a provider
|
|
|
|
In the **AI Providers** section, fill out the **Add Provider** form.
|
|
|
|
| Field | Description |
|
|
| --- | --- |
|
|
| **Label** | A name that helps you recognize the provider, such as `Work OpenAI` or `Personal OpenRouter`. |
|
|
| **Provider** | The provider type, such as OpenAI, Anthropic Claude, Google Gemini, Vercel AI Gateway, OpenRouter, Ollama, or OpenAI-compatible. |
|
|
| **Model** | The exact model name expected by that provider. |
|
|
| **Base URL** | The provider endpoint. Leave the default unless you use a gateway, proxy, local provider, or OpenAI-compatible endpoint. |
|
|
| **API Key** | The key Reactive Resume should use when sending AI requests to that provider. |
|
|
|
|
Click **Save Provider** when the form is complete.
|
|
|
|
<Frame caption="Saved AI provider in Integrations">
|
|
<img
|
|
src="/images/guides/using-ai/screenshot-2.webp"
|
|
alt="Integrations settings showing a saved and tested AI provider"
|
|
/>
|
|
</Frame>
|
|
|
|
<Warning>
|
|
Treat API keys like passwords. Anyone with a key can use the connected provider account and may incur costs.
|
|
</Warning>
|
|
|
|
## Test and enable a provider
|
|
|
|
After saving a provider, test it before using it.
|
|
|
|
<Steps>
|
|
<Step title="Click Test">
|
|
Reactive Resume sends a small request to verify the provider, model, base URL, and key.
|
|
</Step>
|
|
|
|
<Step title="Review the status">
|
|
A successful provider is marked **Tested**. A failed provider is marked **Failed** and may show an error message.
|
|
</Step>
|
|
|
|
<Step title="Enable the provider">
|
|
Turn on **Use** for the tested provider you want Reactive Resume to use.
|
|
</Step>
|
|
</Steps>
|
|
|
|
<Info>
|
|
Only tested providers can be used for AI-assisted features.
|
|
</Info>
|
|
|
|
## How credentials are stored
|
|
|
|
AI provider credentials are encrypted on the server and are never shown again after saving. The settings page only shows a preview of the saved key.
|
|
|
|
If provider management is unavailable, your self-hosted deployment may be missing required server configuration.
|
|
|
|
<Warning>
|
|
AI provider management requires the server-side services used to encrypt credentials. If the page says provider
|
|
management is unavailable, check your deployment configuration before using AI features.
|
|
</Warning>
|
|
|
|
## Where AI is used
|
|
|
|
After a provider is tested and enabled, you can use AI in:
|
|
|
|
- **Resume Analysis** in the builder's right sidebar;
|
|
- **AI-assisted resume changes** from the builder;
|
|
- **Agent** workflows that create isolated AI drafts;
|
|
- **PDF and Microsoft Word imports** from the dashboard import dialog.
|
|
|
|
For the builder workflow, see [Using AI in the builder](/guides/using-ai-in-the-builder). For the dedicated agent workspace, see [Using the AI Agent Workspace](/guides/using-ai-agent) and [AI Agent Tools](/guides/ai-agent-tools). For AI-assisted imports, see [Importing resumes](/guides/importing-resumes).
|