<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Lifan</title>
    <description>The latest articles on DEV Community by Lifan (@lifanbuilds).</description>
    <link>https://dev.to/lifanbuilds</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3940988%2F4a880c11-ad7c-4c4c-8d57-d80abbcbef15.png</url>
      <title>DEV Community: Lifan</title>
      <link>https://dev.to/lifanbuilds</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lifanbuilds"/>
    <language>en</language>
    <item>
      <title>Why Your AI Browser Agent Needs a Local Vault (Not a Cloud Bot Vault or Plaintext .env)</title>
      <dc:creator>Lifan</dc:creator>
      <pubDate>Sat, 07 Nov 2026 03:59:43 +0000</pubDate>
      <link>https://dev.to/lifanbuilds/why-your-ai-browser-agent-needs-a-local-vault-not-a-cloud-bot-vault-or-plaintext-env-5198</link>
      <guid>https://dev.to/lifanbuilds/why-your-ai-browser-agent-needs-a-local-vault-not-a-cloud-bot-vault-or-plaintext-env-5198</guid>
      <description>&lt;p&gt;Give an AI agent a browser task—booking a flight, filling a job application, or reconciling SaaS invoices—and it immediately hits three walls:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Profile ambiguity:&lt;/strong&gt; Which of the three addresses Chrome saved over the last five years is your &lt;em&gt;current home&lt;/em&gt; vs. &lt;em&gt;work&lt;/em&gt; address?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Credentials and payment cards:&lt;/strong&gt; How does the agent sign in or select the right corporate card without you pasting passwords into the prompt or leaving a plaintext &lt;code&gt;.env&lt;/code&gt; / CSV export on disk?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2FA verification:&lt;/strong&gt; When the site sends a 6-digit OTP to Gmail or iMessage, how does the agent read &lt;em&gt;that one code&lt;/em&gt; without turning your inbox into an unrestricted search oracle?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Recently, xAI shipped &lt;strong&gt;Grok Bot Vault&lt;/strong&gt; (&lt;code&gt;v0.75.2+&lt;/code&gt;) with saved Logins, Cards, Contact Info, and natural-language Hints. It proved the exact product category—but also highlighted why a cloud-hosted, vendor-locked bot vault makes security-conscious developers nervous:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In Grok Bot Vault, saved payment cards auto-fill and pay at checkout &lt;strong&gt;without a separate payment confirmation step&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Vault entries are shared globally across all bots on the account.&lt;/li&gt;
&lt;li&gt;Importing logins requires exporting a plaintext &lt;code&gt;&amp;lt;5 MB&lt;/code&gt; CSV file to disk.&lt;/li&gt;
&lt;li&gt;It only works inside Grok Bot—not Claude Code, Codex, Cursor, or OpenClaw.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I built &lt;strong&gt;&lt;a href="https://github.com/lifan-builds/agent-autofill" rel="noopener noreferrer"&gt;Agent Autofill&lt;/a&gt;&lt;/strong&gt; to solve the full loop locally on macOS behind a single MCP server.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Agent Autofill compares
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Capability&lt;/th&gt;
&lt;th&gt;Agent Autofill&lt;/th&gt;
&lt;th&gt;Grok Bot Vault (&lt;code&gt;v0.75.2+&lt;/code&gt;)&lt;/th&gt;
&lt;th&gt;1Password Agentic Autofill&lt;/th&gt;
&lt;th&gt;
&lt;code&gt;personal-vault-mcp&lt;/code&gt; (PCP)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Custody&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Local SQLite (AES-GCM) + macOS Keychain&lt;/td&gt;
&lt;td&gt;xAI Cloud&lt;/td&gt;
&lt;td&gt;1Password Cloud + Local Agent&lt;/td&gt;
&lt;td&gt;Local SQLite&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Works with any MCP agent&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes (Claude, Codex, Cursor, OpenClaw)&lt;/td&gt;
&lt;td&gt;No (Grok Bot only)&lt;/td&gt;
&lt;td&gt;Constrained integrations&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Addresses + Home/Work meaning&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes (Chrome seed + confirmed bundles)&lt;/td&gt;
&lt;td&gt;Basic Contact Info + Hints&lt;/td&gt;
&lt;td&gt;Static identity items&lt;/td&gt;
&lt;td&gt;Identity + Preferences&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Password import without CSV&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Direct Chrome Keychain Safe Storage&lt;/td&gt;
&lt;td&gt;Requires plaintext CSV export&lt;/td&gt;
&lt;td&gt;Native vault&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Secretless browser login&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Local Chrome extension (&lt;code&gt;credential.use&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;Server-side bot runtime&lt;/td&gt;
&lt;td&gt;Browserbase / extension&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Checkout confirmation gate&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Mandatory pre-submit human gate&lt;/td&gt;
&lt;td&gt;Saved cards auto-pay without prompt&lt;/td&gt;
&lt;td&gt;Approval prompt&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Scoped Email + iMessage 2FA&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes (&lt;code&gt;email.otp&lt;/code&gt; + macOS Messages)&lt;/td&gt;
&lt;td&gt;No (manual takeover on 2FA)&lt;/td&gt;
&lt;td&gt;TOTP only&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Architecture: Metadata first, scoped reads second
&lt;/h2&gt;

&lt;p&gt;Agent Autofill separates &lt;strong&gt;choosing&lt;/strong&gt; a record from &lt;strong&gt;reading&lt;/strong&gt; its secret or personal values:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Value-free discovery:&lt;/strong&gt; The agent calls &lt;code&gt;list_profile_groups&lt;/code&gt;, &lt;code&gt;match_credentials&lt;/code&gt;, or &lt;code&gt;match_financial_records&lt;/code&gt; (supporting natural-language &lt;code&gt;hint&lt;/code&gt;, &lt;code&gt;last4&lt;/code&gt;, or &lt;code&gt;card_suffix&lt;/code&gt; comparisons inside the vault). No passwords, card numbers, or street addresses are returned during discovery.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Origin + purpose grants:&lt;/strong&gt; Every sensitive read requires an explicit grant (or a paired local service identity) bound to a normalized &lt;code&gt;target_origin&lt;/code&gt; and &lt;code&gt;purpose&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Two credential delivery paths:&lt;/strong&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Extension handoff (&lt;code&gt;delivery="extension"&lt;/code&gt;):&lt;/strong&gt; Issues a short-lived, origin-bound one-time handle (&lt;code&gt;credential.use&lt;/code&gt;). The paired local Chrome extension fills the login on the matching tab so the password never enters model context.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Direct (&lt;code&gt;delivery="direct"&lt;/code&gt;):&lt;/strong&gt; Returns only the requested fields (&lt;code&gt;username&lt;/code&gt;, &lt;code&gt;password&lt;/code&gt;) for the approved origin when extension handoff isn't used.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Target-bound 2FA extraction:&lt;/strong&gt; &lt;code&gt;request_auth_code_for_recipient&lt;/code&gt; validates sender domain, recipient, and freshness window before returning a single code, and &lt;code&gt;MacMessagesAdapter&lt;/code&gt; reads scoped macOS Messages (including modern macOS &lt;code&gt;attributedBody&lt;/code&gt; &lt;code&gt;typedstream&lt;/code&gt; payloads) in read-only mode.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Hard boundary: Information-only
&lt;/h2&gt;

&lt;p&gt;Agent Autofill never navigates, clicks submit, sends outbound messages, or completes a purchase. Reading a field and submitting a form are two distinct decisions. Even when an agent is authorized to read checkout fields, the consuming workflow must pause and show the final review summary before clicking submit, pay, or send.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it in 60 seconds on macOS
&lt;/h2&gt;

&lt;p&gt;You can run the synthetic in-memory tour before connecting any real database, Keychain entry, or browser profile:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/lifan-builds/agent-autofill.git
&lt;span class="nb"&gt;cd &lt;/span&gt;agent-autofill
uv tool &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nb"&gt;.&lt;/span&gt;

&lt;span class="c"&gt;# 1. Run the memory-only synthetic tour (touches zero real files)&lt;/span&gt;
agent-autofill demo

&lt;span class="c"&gt;# 2. Initialize your encrypted vault and inspect the loopback Inbox&lt;/span&gt;
agent-autofill &lt;span class="nt"&gt;--db&lt;/span&gt; ~/.agent-autofill.sqlite3 init
agent-autofill &lt;span class="nt"&gt;--db&lt;/span&gt; ~/.agent-autofill.sqlite3 quickstart
agent-autofill &lt;span class="nt"&gt;--db&lt;/span&gt; ~/.agent-autofill.sqlite3 inbox-web

&lt;span class="c"&gt;# 3. Register the MCP server with Claude Desktop, Cursor, Codex, or Antigravity&lt;/span&gt;
agent-autofill mcp-install &lt;span class="nt"&gt;--client&lt;/span&gt; claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Agent Autofill is currently &lt;strong&gt;macOS-first&lt;/strong&gt; (using macOS Keychain, Chrome Safe Storage, and &lt;code&gt;chat.db&lt;/code&gt;); Linux and Windows support are on the roadmap.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Repository &amp;amp; 33-second product tour:&lt;/strong&gt; &lt;a href="https://github.com/lifan-builds/agent-autofill" rel="noopener noreferrer"&gt;github.com/lifan-builds/agent-autofill&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>python</category>
      <category>privacy</category>
      <category>ai</category>
      <category>mcp</category>
    </item>
    <item>
      <title>Building Foliofen: a local-first health-record exporter</title>
      <dc:creator>Lifan</dc:creator>
      <pubDate>Tue, 11 Aug 2026 04:58:03 +0000</pubDate>
      <link>https://dev.to/lifanbuilds/building-a-local-first-mychart-exporter-for-a-changing-medical-record-3bob</link>
      <guid>https://dev.to/lifanbuilds/building-a-local-first-mychart-exporter-for-a-changing-medical-record-3bob</guid>
      <description>&lt;p&gt;Foliofen CLI started as a practical family tool.&lt;/p&gt;

&lt;p&gt;While we were caring for a medically complex baby in the NICU, notes and test&lt;br&gt;
results kept changing. I needed a current copy of the records we could already&lt;br&gt;
view, in a form that a local downstream workflow could consume without&lt;br&gt;
rebuilding context by hand.&lt;/p&gt;

&lt;p&gt;The result is a Node.js CLI that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;launches a dedicated Chrome profile&lt;/li&gt;
&lt;li&gt;reads records available to the signed-in MyChart user&lt;/li&gt;
&lt;li&gt;stores normalized records locally&lt;/li&gt;
&lt;li&gt;exports Markdown or chunked JSONL&lt;/li&gt;
&lt;li&gt;validates the active chart before mutating the store&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The CLI does not explain records or make medical decisions. A separate local&lt;br&gt;
workflow used the exports for timely explanations. Keeping those two jobs&lt;br&gt;
separate made the data boundary easier to understand and test.&lt;/p&gt;
&lt;h2&gt;
  
  
  A runnable demo without a chart
&lt;/h2&gt;

&lt;p&gt;Reviewing a health-record export tool should not require sharing a chart. The public beta has&lt;br&gt;
an offline synthetic demo:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/lifan-builds/foliofen-cli.git
&lt;span class="nb"&gt;cd &lt;/span&gt;foliofen-cli
npm &lt;span class="nb"&gt;install
&lt;/span&gt;node src/cli.mjs demo
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After installation, the demo exercises the CLI and JSONL export shape without starting&lt;br&gt;
Chrome, accessing the network, or writing a record store.&lt;/p&gt;

&lt;h2&gt;
  
  
  Privacy choices
&lt;/h2&gt;

&lt;p&gt;The project has no backend, telemetry, cloud sync, or built-in LLM. New installs&lt;br&gt;
use the operating system's application-data directory. Stores, exports,&lt;br&gt;
attachments, and browser metadata use private POSIX permissions.&lt;/p&gt;

&lt;p&gt;The dedicated Chrome profile is still sensitive because it contains cookies.&lt;br&gt;
Exports are medical data. If a user sends an export to another application,&lt;br&gt;
that application's privacy rules apply.&lt;/p&gt;

&lt;p&gt;Public issue templates reject medical records, screenshots, portal URLs, and&lt;br&gt;
credentials. Bugs need synthetic reproductions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Beta scope
&lt;/h2&gt;

&lt;p&gt;The public beta targets macOS, Node.js 20 or newer, and Google Chrome. MyChart&lt;br&gt;
deployments vary, and I expect portal-specific fixes. Foliofen is an independent tool compatible with MyChart® patient portals.&lt;br&gt;
MyChart is a registered trademark of Epic Systems Corporation. Foliofen is not&lt;br&gt;
affiliated with, endorsed by, or sponsored by Epic Systems Corporation or any&lt;br&gt;
health care provider. It does not provide medical advice.&lt;/p&gt;

&lt;p&gt;Repository and setup guide:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/lifan-builds/foliofen-cli" rel="noopener noreferrer"&gt;https://github.com/lifan-builds/foliofen-cli&lt;/a&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>opensource</category>
      <category>privacy</category>
      <category>cli</category>
    </item>
    <item>
      <title>Building a Free Open-Source Tracker for Credit Card Benefits</title>
      <dc:creator>Lifan</dc:creator>
      <pubDate>Tue, 07 Jul 2026 23:20:02 +0000</pubDate>
      <link>https://dev.to/lifanbuilds/building-a-free-open-source-tracker-for-credit-card-benefits-2hcd</link>
      <guid>https://dev.to/lifanbuilds/building-a-free-open-source-tracker-for-credit-card-benefits-2hcd</guid>
      <description>&lt;p&gt;I built &lt;strong&gt;Perks Reminder&lt;/strong&gt;, a free open-source app for tracking credit card benefits, recurring credits, welcome bonus deadlines, annual fee ROI, and loyalty expirations.&lt;/p&gt;

&lt;p&gt;The product problem is simple: recurring benefits are calendar problems.&lt;/p&gt;

&lt;p&gt;A monthly dining credit, an annual hotel credit, a signup bonus deadline, and a points expiration date all need different reminder behavior. They are not hard to track individually, but they become annoying once you have enough of them.&lt;/p&gt;

&lt;p&gt;Live app:&lt;br&gt;
&lt;a href="https://www.perks-reminder.com" rel="noopener noreferrer"&gt;https://www.perks-reminder.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;GitHub:&lt;br&gt;
&lt;a href="https://github.com/lifan-builds/perks-reminder" rel="noopener noreferrer"&gt;https://github.com/lifan-builds/perks-reminder&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Design Constraints
&lt;/h2&gt;

&lt;p&gt;I wanted the app to be useful without becoming a full personal-finance system.&lt;/p&gt;

&lt;p&gt;That led to a few constraints:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;no bank account scraping&lt;/li&gt;
&lt;li&gt;user-controlled card and benefit data&lt;/li&gt;
&lt;li&gt;clear recurring due dates&lt;/li&gt;
&lt;li&gt;email reminders before expiration&lt;/li&gt;
&lt;li&gt;import / export&lt;/li&gt;
&lt;li&gt;mobile-first UI&lt;/li&gt;
&lt;li&gt;self-hostable source&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is not to infer every transaction. The goal is to make the benefits visible enough that users stop missing expiring credits.&lt;/p&gt;

&lt;h2&gt;
  
  
  What It Tracks
&lt;/h2&gt;

&lt;p&gt;Perks Reminder tracks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;recurring card benefits&lt;/li&gt;
&lt;li&gt;welcome bonus deadlines&lt;/li&gt;
&lt;li&gt;annual fee ROI&lt;/li&gt;
&lt;li&gt;complete / partial-complete status&lt;/li&gt;
&lt;li&gt;notes&lt;/li&gt;
&lt;li&gt;custom reminders&lt;/li&gt;
&lt;li&gt;loyalty points and miles expiration&lt;/li&gt;
&lt;li&gt;import / export&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The loyalty tracker is split into a separate subsite:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://loyalty.perks-reminder.com/" rel="noopener noreferrer"&gt;https://loyalty.perks-reminder.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Card benefits and loyalty expiration dates behave differently, so I kept the workflows separate while sharing the login system.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 2.1 Update
&lt;/h2&gt;

&lt;p&gt;The latest update focused on mobile UX and practical benefit usage notes.&lt;/p&gt;

&lt;p&gt;Most users check benefit status from a phone, not from a desktop. So the mobile UI now makes expiring benefits more prominent, makes completion actions faster, and supports views by card, category, and due date.&lt;/p&gt;

&lt;p&gt;The more interesting feature is &lt;strong&gt;Benefit usage manuals&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;For a lot of card credits, the useful information is not only "this card has this benefit." Users also want to know:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;how the credit usually triggers&lt;/li&gt;
&lt;li&gt;which merchants count&lt;/li&gt;
&lt;li&gt;whether gift cards work&lt;/li&gt;
&lt;li&gt;when credits tend to post&lt;/li&gt;
&lt;li&gt;what common traps exist&lt;/li&gt;
&lt;li&gt;whether recent data points changed the answer&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That turns the app from a checklist into a practical operating manual.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tech Stack
&lt;/h2&gt;

&lt;p&gt;The current stack:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Next.js&lt;/li&gt;
&lt;li&gt;React&lt;/li&gt;
&lt;li&gt;Tailwind CSS&lt;/li&gt;
&lt;li&gt;Prisma&lt;/li&gt;
&lt;li&gt;PostgreSQL&lt;/li&gt;
&lt;li&gt;NextAuth&lt;/li&gt;
&lt;li&gt;Resend for email reminders&lt;/li&gt;
&lt;li&gt;Vercel cron jobs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The source is open, and self-hosting is supported for people who want complete control over their data.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Hard Part Is Data Freshness
&lt;/h2&gt;

&lt;p&gt;The hard engineering/product problem is not only reminders. It is maintaining real-world benefit data.&lt;/p&gt;

&lt;p&gt;Card benefits change. Redemption paths change. Merchant coding changes. Community data points become stale.&lt;/p&gt;

&lt;p&gt;That is why the launch asks users to report missing cards, outdated rules, and wrong usage notes.&lt;/p&gt;

&lt;p&gt;I launched the update first on USCardForum/Nitan because the users there know the edge cases:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.uscardforum.com/t/topic/388701" rel="noopener noreferrer"&gt;https://www.uscardforum.com/t/topic/388701&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Feedback Wanted
&lt;/h2&gt;

&lt;p&gt;I would appreciate feedback on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;missing card data&lt;/li&gt;
&lt;li&gt;recurring-benefit modeling&lt;/li&gt;
&lt;li&gt;reminder timing&lt;/li&gt;
&lt;li&gt;self-hosting setup&lt;/li&gt;
&lt;li&gt;import/export workflow&lt;/li&gt;
&lt;li&gt;whether usage manuals are a useful format&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Live app:&lt;br&gt;
&lt;a href="https://www.perks-reminder.com" rel="noopener noreferrer"&gt;https://www.perks-reminder.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;GitHub:&lt;br&gt;
&lt;a href="https://github.com/lifan-builds/perks-reminder" rel="noopener noreferrer"&gt;https://github.com/lifan-builds/perks-reminder&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>nextjs</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
