DEV Community: Levine

Four Ready-Made Mac Widgets for an Indie Developer's Daily Routine

Levine — Wed, 09 Sep 2026 12:55:30 +0000

Check whether your site responds, glance at its search performance, browse a few product launches, then start a focused work session. Four existing Kepo store plugins cover those jobs without requiring you to generate a custom widget first.

We build Kepo, a Mac app with a shortcut-accessible widget panel. This guide focuses on four plugins available in the store today, with their actual published previews and setup details. The screenshots illustrate the interfaces; their numbers and launch listings are examples from those previews, not current measurements.

1. Web Status: keep one website's recent checks in view

The Web Status widget monitors one URL and displays its current reachability alongside a short history of recent checks. It is useful when you want a quick indication that a page you maintain is responding.

Published Web Status preview, showing the wide layout and recent-check history.

Start with a specific page that matters to you: your product homepage, documentation homepage, or another public URL you manage. Set that URL in the widget and compare the first result with opening the page yourself.

The history adds context to a single status indicator. If the recent checks alternate between success and failure, you have a reason to investigate instead of treating one successful response as the whole story.

There are three practical details to remember:

Checks are scheduled. This is not a continuous live probe.
Changing the configured URL resets that widget's old history. Keep separate widgets if you need separate histories.
An excessively short timeout can cause false failures. A slow response and a genuinely unreachable site are different problems.

Use this as a convenient status view. For a production service that requires dependable incident notification, keep your established monitoring and alerting process too.

2. Google Search Console: bring four search metrics into the panel

The Google Search Console widget displays performance numbers for one website property. It is aimed at the recurring check: “How is this site's search performance looking over the period I selected?”

Published Search Console preview. The displayed values are preview data, not a report of today's results.

The setup is short:

Add the component to a Kepo panel.
Open its settings and set Website to your domain, such as example.com.
Choose the time range you want to inspect.
Open the report once and sign in if Google requests it. Your account must have access to the relevant property.

Choose the layout based on the information you need. Small displays clicks and impressions. Wide and large also show click-through rate and average position.

For a practical example, suppose you maintain a product site and a documentation site. Configure a widget for the property you want to review, choose its reporting period, and compare the displayed figures with the same property and period in Search Console. This catches an incorrect domain or time-range selection before it becomes part of your daily routine.

The widget is a compact view of Search Console performance data. It does not turn that data into a live visitor counter. Open the underlying report when you need to examine queries, pages, or a change in more detail.

3. Product Hunt: a compact list for launch discovery

The Product Hunt feed widget shows recent launches from Kepo's hosted Product Hunt feed. It brings product names, descriptions, icons, and links into a small browsing surface.

Published Product Hunt preview. Products, dates, and counts reflect the preview rather than the current launch list.

For an indie developer, this can be a useful place to discover how other makers describe a problem, package a feature, or present a product. Scan the list, choose one relevant launch, and follow its link when you want the full context.

The feed can include richer details such as votes, comments, ranks, topics, and makers. The plugin documentation specifies that counts, ranks, makers, and icons are read from the official API when available. Do not assume every item will always have every field.

A good way to use this component is to put a time boundary around discovery. Give yourself a short browsing window, save one idea worth investigating, and return to your own work. A compact feed is most useful when it supports that habit.

4. Pomodoro Clock: start work after the checks

The Pomodoro Clock widget supports work sessions, breaks, and recent completion records. It gives the panel an action you can take after checking the other widgets: start the next task.

Published Pomodoro Clock preview. The wide layout includes recent completion records.

The defaults are 25 minutes of work and 5 minutes of break time. Both durations can be changed in the widget settings. Available actions include start, pause, resume, finish, and reset.

To try it, choose one concrete task—such as drafting a changelog or fixing a small bug—then start a work session. Pause if you need to interrupt it, resume when you return, and switch to a break when appropriate.

Completed work sessions are stored locally. The wide layout shows recent records, which makes it useful when you want to look back at completed sessions. The plugin requires no login and does not open a browser.

Those records belong to the local widget data. Clearing that data removes them, so they should not be your only record if you need durable time tracking.

Choose a small starting layout

You can find all four in the Kepo widget store. This is a suggested arrangement rather than a requirement to install everything:

Component	What it helps you do	Useful layout choice	Key dependency
Web Status	Check one URL and its recent history	Wide for visible history	Valid URL and scheduled checks
Search Console	Review one property's search performance	Wide or large for four metrics	Google access and the selected reporting period
Product Hunt	Discover recent product launches	Large for more reading space	Kepo's hosted feed and available source fields
Pomodoro Clock	Run focus sessions and breaks	Wide for recent records	Local widget data

Start with two components if that covers your routine. Add a third when you have a recurring reason to check it. Kepo's Mac desktop widgets overview explains how these components fit into a panel you can bring up with Option + Space.

Three questions before you install

Do these four plugins require AI generation? No. These are existing store plugins. Install the relevant plugin and configure the component you want to use.

Does every widget need an account? No. Pomodoro Clock requires no login. Search Console needs access to your Google property. Check each plugin's setup notes rather than assuming all components share the same requirements.

Are the screenshots showing live results? No. They are the actual preview images published with the store versions. Verify your own widget's configured source and results after installation.

Which would earn a place in your daily panel: website checks, search metrics, launch discovery, or a focus timer?

Kepo: GitHub, RSS, and Developer Tools in One Mac Widget Panel

Levine — Wed, 09 Sep 2026 03:07:13 +0000

A pull request waiting for review, a library release, and a JSON payload to inspect are small tasks. They do not each need a permanent browser tab. Kepo brings those checks and utilities into a Mac widget panel that you can open with a keyboard shortcut.

We build Kepo, and this is a practical introduction to the product: what you can put in the panel today, how to start with a useful setup, and where the limits are.

Start with three widgets you will actually use

A useful panel should answer a few recurring questions. For a developer, a reasonable starting point is: Does anything need my review? Has a dependency released an update? Can I inspect this data without opening another utility site?

Here are three existing plugins that cover those jobs.

1. GitHub: review requests and repository updates

The Kepo GitHub widgets include a notifications inbox, review requests, release tracking, tag tracking, a commit timeline, and trending repositories.

For a focused setup, add Review Requests and Release Watch. The first surfaces pull requests requesting your review; the second follows releases for a particular repository. You can open GitHub when something needs attention instead of repeatedly navigating there to check.

Configuration matters:

Notifications and review requests need a signed-in GitHub session.
Repository widgets need the exact owner/repo identifier.
The commit timeline also needs the repository's actual branch name. Do not assume every project uses main.

For example, to follow a dependency, copy its repository identifier from GitHub and use that in Release Watch. Check the initial result against the repository's release page before relying on it.

These views depend on GitHub's pages. If GitHub changes its page structure, a plugin update may be needed.

2. Developer Tools: keep small conversions close to your editor

The Developer Tools widgets provide ten utilities, including JSON formatting, JWT inspection, regular-expression testing, text comparison, timestamp conversion, and cron parsing.

A simple first choice is JSON Formatter. Add a wide widget if you prefer input and output side by side, then try a small sample:

{"service":"demo","healthy":true,"checks":["http","database"]}

Formatting makes the structure easier to inspect; validation helps distinguish malformed input from a display problem. The formatter processes the text locally rather than sending the payload to a formatting website.

Choose the widget size for the task. JSON Formatter supports wide and large layouts. Text Diff, Regex Tester, and JWT Inspector use the large layout because they need more room for their inputs and results.

Local utilities are useful for quick inspection, but the plugin is not a secret vault. Start with sample data when evaluating a tool, and follow your team's rules for handling credentials and production data.

3. RSS: follow a specific source

The Kepo RSS Reader widget displays recent items from a public RSS or Atom feed and links to the original articles.

One widget reads one feed. To follow a project blog and a separate engineering newsletter, create two widgets with their respective feed URLs. A normal website homepage is not necessarily a feed URL; use the RSS or Atom address provided by the publisher.

That makes the setup deliberately specific: choose the sources you want to check, then open an original article when its title is relevant. Feed freshness and completeness depend on the publisher. An empty or broken source can produce an empty result or an error.

Put the panel together

Here is a small configuration to try before filling the screen with widgets:

Recurring task	Component	What to configure
Find work awaiting review	GitHub Review Requests	Your signed-in GitHub session
Track a dependency	GitHub Release Watch	The exact repository identifier
Inspect structured data	JSON Formatter	Sample JSON; wide or large layout
Follow a project blog	RSS Reader	A valid public RSS or Atom URL

Download the Mac app, choose the relevant plugins from the Kepo widget store, and add the components you need. Configure each data source and compare its first result with the original source.

Kepo's shortcut-accessible panel lets you bring these widgets into view with Option + Space. Keep only the components that help you make a decision or complete a small task. A crowded panel can become another place to get distracted.

What if the widget you need does not exist?

Kepo also supports creating and editing widgets with AI. Describe the source, the information you want to see, and the layout you need. Our Mac desktop widgets overview explains that approach alongside the ready-made options.

A useful request is specific: “Show the latest five entries from this public RSS feed, with the title and publication date. Open the original article when I click an entry.” Include the actual feed URL when you try it.

Treat the generated result as something to verify: is it reading the intended source, showing the expected items, and handling a failed request clearly? Website access, login requirements, and changes to page structure still matter. An AI-generated widget does not remove those dependencies.

Try one recurring check first

Kepo is currently available for Mac, with a Windows waitlist on the homepage. The free plan includes one panel and the ability to install and use store plugins; AI features and limits vary by plan.

Start with one check you already repeat during the day. If it belongs in a widget, add it, verify the result, and see whether you keep using it.

For developers here: which small task would you put in a shortcut-accessible panel first—review requests, release tracking, a local utility, or something else?

MVP Embodied AI: Five Demos Point to a Self-Evolving Robotics Model

Levine — Wed, 02 Sep 2026 07:25:04 +0000

English translation and media publication. Reporting credited to QbitAI / Noah. The original media is published with authorization.

A mysterious embodied-AI team has released a run of striking demos around its internal MVP (Make Veritable People) model. The demonstrations suggest a system designed to unify physical reasoning, long-horizon planning, and human-like behavior.

The long single-take introduction led observers to ask whether embodied intelligence may be approaching a ChatGPT-like moment. The team argues that the robot is not merely predicting likely motions: it understands physical constraints, human habits, and its own capabilities.

Demo 1: Hand-eye coordination and dynamics

Holding water while absorbing a disturbance, then stabilizing falling cans with the other hand, the robot appears to combine fast reactions with an internal model of dynamics.

Demo 2: Space, object properties, and household habits

The robot sorts a living room zero-shot: it returns objects to their places, drags a basket across a smooth floor, hangs loop-shaped objects, and tosses a cushion onto a sofa when that is the lower-effort action.

Demo 3: Cross-embodiment collaboration

Two robots with different bodies work together to flatten and shake a bedsheet. The behavior suggests one shared policy can coordinate across embodiments while preserving the logic of a familiar human task.

Demo 4: Energy-driven action selection

Rather than shuttle items one by one, the robot carries several objects at once, using its own body as a temporary organizer. This reflects an action policy that appears to seek lower-effort, long-horizon solutions.

Why it matters

Across the demos, MVP appears to pursue consistent movement, sustained task completion, physical awareness, and a distinctive style of action. If these behaviors generalize outside the controlled scenes, embodied AI may be moving closer to useful everyday autonomy.

All performance claims are attributed to the original QbitAI report and the model team it interviewed.