✦ How it works

From your daily.dev profile
to a structured learning path

DevPath uses your reading habits and interests as raw signal, then lets GPT-4o do the curriculum design — so you spend time learning, not planning.

01

Grab your two API keys

You need two keys to get started. First, go to app.daily.dev/settings/api and generate a Personal Access Token (requires a daily.dev Plus subscription). Second, grab an OpenAI API key from platform.openai.com/api-keys — DevPath uses GPT-4o on your own account so you only pay for what you generate. Both keys are stored only in your browser and never on our servers.

02

Set up your profile once

Head to your Profile page and answer 4 quick questions: your experience level, primary role, learning goal, and preferred style. You can also describe what you're currently struggling with. These answers are saved in your browser and automatically included in every path you generate — you never have to answer them again. Update them anytime as you grow.

03

Pick your topics — or let AI suggest

On the Generate page, enter your API keys and either select 1–3 topics manually (React, System Design, DevOps, or anything custom) or click "Suggest paths for me". The suggestion feature fetches your bookmarks and followed tags, then asks GPT-4o to recommend 3 distinct, personalised path topics based on what you've actually been reading. One click on "Take →" and your path starts building.

04

AI builds your personal path

DevPath fetches your bookmarks, followed tags, and tech stack from daily.dev. GPT-4o selects 12–18 relevant articles and organises them into 3–5 learning stages, ordered from foundational to advanced — with a personalised reason for each article that references your actual stack, tags, and profile background.

05

Work through your stages

Each article has an [→ Open] link that takes you directly to the post on daily.dev. Mark articles as read as you go — your progress is saved in your browser and visualised with a circuit-line sidebar. All your generated paths are accessible from the My Paths page, with per-path completion percentages so you can pick up where you left off.

06

Share your path

Every path gets a shareable URL that works in any browser — the full path is compressed and encoded directly into the link, so anyone can open it without an account or the same browser. Share to Twitter/X or LinkedIn with one click.

FAQ

What data does DevPath access?

Your daily.dev bookmarks, followed tags, and tech stack — fetched once per generation using your PAT. DevPath never stores this data on a server.

Where are my paths and profile stored?

Entirely in your browser's localStorage. There's no database. Your profile answers, generated paths, and reading progress all live in your browser — clearing browser data will remove them.

Do I have to fill in my profile every time?

No. Your profile (experience, role, goal, learning style) is saved once and automatically applied to every path you generate. You only need to update it when something changes.

What does the "Suggest paths for me" feature do?

It fetches your bookmarks and followed tags from daily.dev, then makes a lightweight GPT-4o call to suggest 3 personalised path topics based on what you've actually been reading. Clicking "Take →" immediately generates the full path for that topic.

Do I need a daily.dev Plus subscription?

Yes — the daily.dev Public API requires Plus to generate a Personal Access Token. The subscription is with daily.dev, not DevPath.

Do I need my own OpenAI API key?

Yes. DevPath uses GPT-4o on your own OpenAI account so you control costs and your data never passes through our servers. A typical path generation costs a few cents.

What model powers the path generation?

OpenAI GPT-4o with JSON mode, which guarantees a structured, parseable response every time. Your profile background is included in the prompt so the model can personalise article selection and explanations.

Can I share my path with someone else?

Yes — shared links work in any browser. The full path is compressed and encoded into the URL itself, so the recipient can open it without an account or the same browser.