Support — DEV New Tab (unofficial)

DEV New Tab (unofficial) replaces your Chrome New Tab page with a DEV community feed, with public article discovery, local saving, and features for your existing DEV account. It is published by Axrisi, operated by I/E Niko in Tbilisi, Georgia. This is an unofficial community application, not created or endorsed by the DEV team.

Contact support

Email support@axrisi.com for help. Mention DEV New Tab (unofficial) so we can identify the product you are asking about.

Report a bug

Please include:

• Your browser name and version.
• The extension version, available in Chrome's Extensions manager.
• Steps to reproduce the issue, what you expected, and what happened instead.
• An optional screenshot with sensitive information removed.

Do not send passwords, API keys, session cookies, or other credentials. Before attaching a screenshot, remove any private account information or sensitive shortcut URLs.

Frequently asked questions

How do I use account-backed features?

Sign into DEV at dev.to in the same browser profile as the extension. The extension uses your existing DEV session for features such as your reading list, likes, followed topics, and notification count.

Can I use it without signing in?

Yes. Public discovery and local saving work without sign-in.

Do I need an API key or an Axrisi account?

No API key or separate Axrisi account is required for normal use.

What can I customize?

Preferences include theme, compact sidebar, custom shortcuts, feed layout, article previews, and default-on controls for short paragraph overviews in opened article previews, automatic overviews with ready models, visible-card, hover/focus or opt-in all-fetched preloading, and persistent overview caching with ordinary and saved/history retention controls. Translation and article questions are currently hidden behind an internal release flag.

Can I prepare all fetched article overviews?

Yes. Choose Preload all fetched articles in Preferences. Eligible loaded articles, including offscreen cards and articles added through Load more, are queued one at a time. This mode bypasses the visible 3/5-card limit and ordinary preload start budget, but does not fetch more feed pages automatically. Cached or excluded articles are skipped. Models must already be ready, new work pauses while hidden, and cache limits stay the same. It can use more device resources than visible-card preparation.

How do favorite topics differ from Following?

Favorite topics are local shortcuts. They appear alongside your DEV followed tags, with duplicates removed. Clicking a topic opens its public tag feed; editing the shortcuts does not follow tags on DEV or change the Following feed. DEV followed tags help its personalized For you feed, while Following is DEV's people and organization feed.

What do the different feeds show?

For you uses DEV's personalized recommendations; signed-out users see public Discover. Curated shows community-favorited picks, most recently curated first. Latest shows newest published posts. Top ranks posts published within the selected week, month, or year using DEV's score. Following is DEV's people and organization feed.

Can I hide quick posts?

Yes. Preferences hides explicitly marked DEV quick posts by default. It uses DEV's post type rather than guessing from length or reading time, so genuine short articles remain. Saved items and history stay visible. API results without a reliable format marker are kept.

Why is an AI action unavailable?

Built-in AI support depends on the browser, device, available model, and language pair. A Chromium-based browser does not automatically support every API. Preferences and article previews show the detected availability. Models download only after an explicit action; no cloud AI fallback or API key is used. The regular feed and Read on DEV remain usable.

How do article overviews work?

Click a card to open its short overview, or use the hover Read article button to go directly to DEV. Overviews use full public article text, not just its feed description. The preview includes author information, DEV reaction controls, bookmarking and sharing; it does not contain a full-article reading tab. AI can make mistakes, so verify answers with the original article.

Before an AI overview is ready, a DEV description may appear. That text comes from the article's public listing description and may differ from the article body. Public author details are prepared for all fetched articles after the feed renders, with visible authors first. Author loading continues while you browse previews and while summary bodies load, with normal DEV request pacing. Hover, preloading and opened previews share requests. Public profiles persist for 30 days within a 500-profile, 1-MB browser-local cache. Cached bios appear immediately; cold loading reserves space so the sharing section stays steady.

Author-cache expiry starts when a profile is fetched and does not reset when you read it. Profiles refresh after expiry, so a bio may reflect the cached version for up to 30 days. A first-time profile may briefly show Loading author details if opened before preparation finishes. AI/body-cache clearing is separate; uninstalling or clearing extension data removes the public author cache too.

Feed cards do not display generated overviews. Switching For you, Latest, or Top immediately offers that feed's uncached visible articles for bounded preparation; it does not wait for the five-minute feed cache to expire. A started overview continues after closing its preview or changing feeds. Reopening attaches to the same job or cached result. Explicit Cancel stops a job; new preloads pause while the tab is hidden.

How do I share a selected passage?

To share only part of an overview or DEV description, select the desired text and use Snapshot, Copy + source, or Copy text in the floating toolbar. Alt+S focuses those actions. The three-dot menu copies or saves the full overview. Image cards are rendered locally with content-sized layouts and article attribution; these actions never post automatically.

Can I turn AI off or remove its cached data?

Yes. Open Preferences to disable on-device AI or individual features, turn preloading off, or clear stored AI results and article text. Ordinary overviews persist for 7, 14, or 30 days; saved/history overviews for 90, 180, or 365 days. Defaults are 7 and 180 days, within a shared 500-entry/1.5-MB cap. Turning AI or AI caching off removes stored overviews. Article bodies and retained advanced-tool conversations remain session-only. Offline AI needs a cached model and previously available article text; a fresh article still requires a DEV connection.

How often does the notification count update?

Notification counts are event-driven, not continuously polled. Relevant events can request an update, and successful results use a shared 60-second cache, so a count may briefly reflect a cached result.

How do I restore my browser's New Tab behavior?

Open Chrome's Extensions manager by entering chrome://extensions in the address bar. Find DEV New Tab (unofficial) and switch it off to disable it, or choose Remove and confirm to uninstall it. Then open a new tab. Chrome will use its default New Tab page or another enabled New Tab extension. Disabling keeps local extension data; uninstalling removes it.

Privacy

Read the Privacy Policy — DEV New Tab (unofficial) for details about DEV requests, local storage, and support correspondence.