DEV Community: Dongsheng

agent-usage NEW8: agents can torch a 5-hour window with no estimate

Dongsheng — Sun, 20 Sep 2026 03:46:26 +0000

Agents that spawn agents can torch a 5-hour window with no estimate and no confirm.

agent-usage keeps a local honest dashboard — by agent, billing domain, and model.

Menubar remains roadmap (not shipped).

npm i -g agent-usage-all-in-one
agent-usage

Repo: https://github.com/Blackman99/agent-usage-all-in-one · MIT · macOS + Node 24+

Local charts. No auto-switch. Advice only.

agent-usage 0.10.0: charts by agent, billing domain, and model

Dongsheng — Fri, 18 Sep 2026 01:15:17 +0000

agent-usage 0.10.0 is live on npm — a local multi-agent usage dashboard with charts split by agent / billing domain / model.

Honest local dashboard (vs glance-style menubar tools): see where quota and spend actually go across Codex, Claude Code, OpenCode, Grok, and more. Cursor connector is still experimental. Menubar remains roadmap (not shipped).

npm i -g agent-usage-all-in-one
agent-usage

Repo: https://github.com/Blackman99/agent-usage-all-in-one
npm: agent-usage-all-in-one · MIT · macOS + Node 24+

Local charts. No auto-switch. Advice only.

Real Bot: persistent AI teammates on your Mac (local multi-bot · MIT · BYO)

Dongsheng — Thu, 17 Sep 2026 03:53:56 +0000

Not affiliated with xAI or Grok.

I built Real Bot for local multi-bot teammates on your Mac — named bots with duties, groups, @mentions and handoffs — that stay on your machine.

What you get

Local multi-bot — one-to-one, groups, hand work between bots; window, daemon, sessions and one shared workspace folder on your Mac
MIT + BYO — open source (MIT); bring any OpenAI-compatible endpoint
Approval cards — risky actions wait for you; keys go to Keychain
MCP everywhere — stdio or Streamable HTTP, available to every bot

Status

Alpha, macOS only. Unsigned .dmg from Releases.

Website: https://blackman99.github.io/real-bot/

MIT licensed. Again: not affiliated with xAI / Grok — independent open project.

codsh 0.23.0 — Mission Contract: `/ship` that won't silently drift

Dongsheng — Thu, 17 Sep 2026 01:23:56 +0000

codsh is a DeepSeek-native terminal coding agent on open dsh. It is not a Claude Code env wrapper.

The hook stays the same: /ship takes one sentence to verified code.

0.23.0 ships the Mission Contract control plane for that loop — so acceptance criteria stay sealed, drift blocks the run instead of rewriting the goal, and delivery needs recorded evidence.

What changed in 0.23.0

When Gate 1 confirms the spec, /ship compiles a machine-checkable Mission Contract (mission.contract.json) from the sealed Main Track, Out of Scope, and acceptance criteria.

After seal:

Immutable — Main Track, Out of Scope, grill decisions, original wording, acceptance criteria, and the contract JSON. Protected writes are refused; external drift stops the run and stays on disk for inspection.
Alignment Gate — refuses writes that lack requirement mapping or hit immutable memory.
Drift Detector — scores plan/action drift against the seal; a rewritten Main Track is a blocker, not an accepted rewrite.
Verifier — matches acceptance criteria to recorded evidence. Delivery does not complete without it.

Also in this release: wayfinder before the grill interview (destination + open decisions, separate from implementation), and tighter parent/subagent coordination — one parent-owned ticket per turn, fresh-context children for investigation / landing / review, parent keeps questions, gates, and final proofs.

npm: codsh-cli + codsh-bundle 0.23.0.

Why this matters vs “just chat a plan”

Ad-hoc agent plans live in conversation memory. They drift. Acceptance becomes vibes.

/ship keeps the human projection in Markdown and the runner-owned contract on disk:

Pre-flight → wayfinder → grill
Spec (Gate 1) → Tickets (Gate 2)
Landing (TDD) → evidence-based Done

While work is in flight you get a panorama: TTY overlay (Ctrl+G), a ticket-count teaser with the local Web flowchart URL, and the flowchart itself — /ship does not auto-open a browser.

Coming from Claude Code / Codex? Different harness, different product. Redirecting Claude Code at DeepSeek with env vars works; this is the native path on dsh. Map what maps / what’s missing on issue #64.

What `/ship` builds (gallery)

Every gallery project started from a one-sentence request. Real screenshots and playable results: blackman99.github.io/codsh/gallery.html

(Publishing: upload local PNGs from /workspace/codsh-assets/gallery-0.23.0/ as cover + inline if Dev.to prefers hosted uploads.)

Install (60 seconds)

npm install -g @deepseek-ai/dsh codsh-cli
export DEEPSEEK_API_KEY=…   # or any OpenAI-compatible route via ~/.dsh/settings.yaml
codsh

Node ≥22.19. Already on a matching dsh? npm i -g codsh-cli is enough.

Then:

/ship let long diffs open in a pager instead of scrolling past

For tiny edits, plain chat or ⇧Tab plan mode is enough — /ship is multi-phase and burns tokens on purpose.

Agent Usage: One local dashboard for Codex, Claude Code, OpenCode, Grok & more

Dongsheng — Fri, 11 Sep 2026 09:19:54 +0000

Many of us now keep more than one coding agent: Codex for one workflow, Claude Code for another, maybe Grok, OpenCode, dsh, or Antigravity on the side. Usage lives in different UIs — five-hour windows next to weekly caps next to “All models” labels — and cost language mixes subscriptions, client estimates, and API list prices until nothing is comparable.

Agent Usage is a macOS-first, fully local multi-agent usage center. One command opens a dashboard for native quota windows and reset times, tokens and model rankings, history/diagnostics, and a public API retail equivalent for eligible usage. It offers advice only and never switches agents automatically.

Repo: https://github.com/Blackman99/agent-usage-all-in-one
Compare docs: https://github.com/Blackman99/agent-usage-all-in-one/blob/main/docs/comparison.md
npm: agent-usage-all-in-one · CLI: agent-usage · MIT
Requires macOS + Node.js 24+
No Cursor coverage yet · don’t read the package name as “every agent on earth”

Quick start

npx agent-usage-all-in-one
agent-usage The API retail equivalent is **not a bill**. Unknown prices stay **unpriced** — never guessed as `$0`. **Grok Build/SuperGrok** and **xAI API** are independent billing domains and are **never summed**.

### Light comparison

Peers worth naming honestly (see docs/named-competitors.md):

- **ccusage** — CLI reports; we lead with Dashboard + native quotas
- **CodeBurn** — multi-tool/multi-platform; we lean stricter cost semantics + default no telemetry
- **tokscale** — token/cost scale peer; same honesty boundaries apply
- **Token Monitor** — closest dashboard shape; we do **not** claim Cursor / multi-machine / menu bar yet

### Feedback asks

1. Which connector should deepen first?
2. Does retail-equivalent framing help or confuse?
3. What would make `start-at-login` a habit?

PRs/issues welcome. Don’t paste Keychain secrets or live exports.

Prefer npx; global install optional. Daemon binds 127.0.0.1. Data under ~/Library/Application Support/Agent Usage.

Cost honesty

Actual charges, provider estimates, fixed subscription fees, and API retail equivalents are separate evidence.

svelte5plus-calendar: Zero-dependency full calendar for Svelte 5

Dongsheng — Thu, 10 Sep 2026 12:03:39 +0000

The problem

If you’re on Svelte 5, calendar UIs often mean wrapping a React-era library, accepting a heavy dependency tree, or rolling month grids yourself and stopping short of week time-grids, recurrence, and drag-resize. You want one component that feels like Google / Apple / Outlook — without dragging half of npm into the client.

What it is

svelte5plus-calendar is a full-featured, zero-runtime-dependency calendar component for Svelte 5: month, week, day, year, and agenda views, drag & drop editing, recurring events, multiple calendars, i18n, and dark mode. TypeScript-first; styles import automatically.

Docs with live examples: blackman99.github.io/svelte5plus-calendar

Source: github.com/Blackman99/svelte5plus-calendar (MIT)

npm: svelte5plus-calendar

What you get

Six views

Month (spanning multi-day bars, +N more popovers), week & day time grids, year overview, agenda list, and a resources view (rooms/people columns) for booking-style UIs.

Drag & drop

Move events across days/slots, drag all-day bars, resize from the bottom edge, drag empty space to select/create. Touch: long-press to drag, swipe to scroll.

Built-in popovers

Click an event for details (with delete); click/drag empty space for quick-create — zero config. Your callbacks replace them when provided.

Recurring events

Practical RRULE subset (FREQ, INTERVAL, COUNT, UNTIL, BYDAY incl. 2TU/-1FR, BYMONTHDAY) as strings or typed objects, plus exdates. This event and this and following edits; occurrence/series deletion.

Theming & i18n

Light / dark / auto; every color, radius, and font is a CSS custom property; 10-color event palette that adapts to dark mode. Any BCP-47 locale via Intl (no bundles); UI strings for 10 languages; locale-aware week start and clock; timeZone prop with edits converted back.

More

Multiple calendar sources with visibility and edit permissions; current-time indicator and business hours; validRange + eventOverlap={false}; ICS parseICS / toICS; custom eventContent snippets; headless exports (layoutDay, expandRecurrence, …); keyboard navigation and aria-live.

Quick start

npm install svelte5plus-calendar

Requires Svelte 5. Styles are imported automatically.

<script lang="ts">
    import type { CalendarEvent } from 'svelte5plus-calendar';
    import { Calendar } from 'svelte5plus-calendar';

    let events = $state<CalendarEvent[]>([
        {
            id: '1',
            title: 'Kickoff meeting',
            start: new Date(2026, 7, 13, 10, 0),
            end: new Date(2026, 7, 13, 11, 0),
            color: 'teal'
        },
        {
            id: '3',
            title: 'Standup',
            start: new Date(2026, 7, 10, 9, 30),
            end: new Date(2026, 7, 10, 9, 45),
            recurrence: 'FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR'
        }
    ]);
</script>

<div style="height: 640px">
    <Calendar bind:events view="week" locale="en" editable selectable />
</div>

Handle edits with rollback:

<Calendar
    bind:events
    editable
    onEventChange={async ({ event, start, end, revert }) => {
        try {
            await api.update(event.id, { start, end });
        } catch {
            revert();
        }
    }}
/>

Who it’s for

Svelte 5 apps that need a real calendar, not only a date picker
Teams that want DnD + recurrence + i18n without a React interop layer
Authors who prefer CSS-variable theming and headless layout utils

Who it’s not (yet) for

Projects stuck on Svelte 4 (this package requires Svelte 5)
Apps that need a full RFC5545 / CalDAV server stack (client component + practical RRULE subset)
Teams standardized on FullCalendar’s plugin ecosystem with sunk cost already paid

Light comparison (not a roast)

Need	Typical pick	svelte5plus-calendar angle
Battle-tested React calendar	FullCalendar	Svelte 5-native, zero runtime deps
Month-only picker	Lightweight date libs	Full views + DnD + RRULE + resources
Stay in Svelte	DIY grids	One component + docs site examples

Try it / tell us what’s wrong

We’re especially hungry for feedback on:

First-hour DX (npm install → editable week view)
RRULE edit/split edges in real product data
Gaps vs FullCalendar for your booking / scheduling use case

👉 Live docs · GitHub · npm

Comment with your current Svelte calendar approach and the one feature that would make you switch — we’ll prioritize from real replies.

svelte-json-discovery: the discovery.js JSON struct view, as a Svelte 5 component

Dongsheng — Thu, 10 Sep 2026 11:48:33 +0000

discovery.js ships one of the best interactive JSON struct viewers in the wild. If you want that UX inside a Svelte 5 app — search, diff, validate, table, accessibility — without hosting the entire Discovery toolkit, svelte-json-discovery is a standalone extraction/reimplementation.

GitHub: https://github.com/Blackman99/svelte-json-discovery
Docs & examples: https://blackman99.github.io/svelte-json-discovery/
npm: svelte-json-discovery

Install

pnpm add svelte-json-discovery
# or npm / yarn

<script>
  import { JsonViewer } from 'svelte-json-discovery';

  const data = {
    user: { id: 1, name: 'Ada' },
    tags: ['svelte', 'json'],
  };
</script>

<JsonViewer {data} expanded={2} />

Highlights

Area	What you get
Previews	Type-colored tokens; numbers with visual thousands separators; `Date` / `RegExp` / `Set` / Error / bigint / typed arrays / functions
Scale	Windowed large array
Table	Configurable object-array table with bounded “show more”
Diff	Bounded, entity-aware moves; cycle / hostile-value protection
Validate	Async/precomputed issues; optional Ajv / Zod / Valibot adapters
A11y	ARIA tree, roving tabindex, full keyboard navigation
Schema	Hover field docs from JSON Schema (title, description, enum, deprecated, …)
Theme	Light / dark / auto via `--discovery-fmt-*`

Full prop reference: docs #api and the package README under packages/svelte-json-discovery.

Monorepo layout

Path	Role
`packages/svelte-json-discovery`	Published library
`docs`	Docs site consuming the workspace package (examples = shipping code)

Credits & license

All rendering logic, styling, and UX derive from discovery.js src/views/struct/ by Roman Dvornov and contributors. This project re-implements that view as a Svelte 5 component. MIT.

Call for feedback

Still early. If you build API explorers, admin consoles, or schema-driven UIs on Svelte 5, I’d love sharp edges filed as issues — especially large payloads, diff caps, and validator adapter ergonomics.s/objects; incremental Set/Map iterators |
| Strings | Truncation, length badges, escaped vs “as text”, URL auto-link |
| Search | Cancellable key/value walk, capped results, wraparound + reveal |
| Control | Controlled paths + bind:this controller methods (expand, focus, scroll, select) |
| Inspector | Optional accessible toolbar from svelte-json-discovery/inspector |

Bring Claude Code and Codex into Feishu/Lark group chat — with permission cards

Dongsheng — Thu, 10 Sep 2026 11:38:05 +0000

If your team lives in Feishu / Lark, but coding agents live in personal terminals, you get lost context, verbal “is it OK to run that?”, and no shared session.

agent-feishu-channel bridges Claude Code and Codex sessions into a Feishu bot — a complete coding-agent workflow inside group chat.

npm: agent-feishu-channel
CLI: afc
Repo: https://github.com/Blackman99/agent-feishu-channel
Docs: https://blackman99.github.io/agent-feishu-channel/

Why this exists

Chat is where decisions happen. The agent should show up there with local-style controls: approve dangerous tools, keep sessions across restarts, and switch providers without rewiring the bot.

What it does

Dual providers: Claude or Codex; /provider per session
Permission brokering: sensitive calls become Feishu approval cards
Session persistence: survives restarts; auto-resume; /sessions and /resume
Queue & interrupt: messages queue while generating; ! interrupts
Interactive cards: streaming status and tool activity
Runtime config: /config set without restart
Context mitigation: early warnings and a 50MB hard-reset fallback

Quick start

Needs Node.js ≥ 20, a Feishu bot app at open.feishu.cn, and claude and/or codex on $PATH. Install with npm install -g agent-feishu-channel, then run afc init and fill in app_id, app_secret, and the access allowlist before running afc.

Migrating from claude-feishu-channel? The command is now afc (was cfc); state auto-renames and history is kept.

Commands and caveats

/new /stop /status /cost /context /compact /provider /mode /model /config set /project /cd /memory

Permission modes: default, acceptEdits, plan, bypassPermissions. You own Feishu credentials and the allowed_open_ids allowlist; don’t default to bypassPermissions in shared groups.

MIT. Issues: https://github.com/Blackman99/agent-feishu-channel/issues

SveltePress: Ship docs and blogs with SvelteKit — and Svelte 5 inside Markdown

Dongsheng — Thu, 10 Sep 2026 11:13:59 +0000

The problem

If your product is SvelteKit, your docs often… aren’t. You jump to VitePress (Vue) or Docusaurus (React), then maintain a second mental model for layouts, components, and deploy adapters. That’s fine for many teams — until you want interactive examples that are the same components your app uses.

What SveltePress is

SveltePress is a content-centered site builder for docs and blogs, inspired by VitePress and built on SvelteKit. You write Markdown (and Svelte), keep Kit’s full surface area (SSR, SSG, adapters, +page.server.js, hooks), and get documentation-native features on top.

Live docs & demos: sveltepress.site

Source: github.com/SveltePress/sveltepress (~532 stars, MIT)

What you get

Svelte 5 Runes in Markdown

Embed reactive components and $state islands directly in .md — tips/callouts, Twoslash hover types, no separate playground toolchain required for simple demos.

Immutable document versioning

Keep current docs at clean URLs while publishing frozen historical snapshots, with built-in version navigation and release change catalogs.

Built-in i18n

Serve multiple locales from one site: automatic prefixing, language switcher, navigation that preserves the selected version.

Search that stays out of your way

Zero-config Pagefind (client-side, multi-locale filtering, historical index freezing). Algolia DocSearch is also supported if you already live there.

Themes you can own

Default documentation theme, blog theme, or a custom theme — configuration and theme APIs are typed.

Still SvelteKit

Same routing mental model (src/routes/+page.md, layouts, etc.). Scaffold defaults to adapter-static; swap adapters when you need SSR or platform-specific deploys.

Quickstart

# Node.js ^20.19.0 or >=22.12.0; pnpm 10 recommended
npm create @sveltepress@latest
# or: pnpm create @sveltepress

cd your-project
pnpm install
pnpm dev

Docs walk through adding @sveltepress/vite to an existing SvelteKit app if you’re not starting from scratch.

Who it’s for

Svelte / SvelteKit teams who want docs or a content site without leaving the ecosystem
Projects that need versioned docs and/or multi-locale sites
Authors who want interactive Svelte examples next to prose

Who it’s not (yet) for

Teams standardized on Vue/React doc stacks with deep plugin ecosystems already paid for
Pure “Markdown → HTML with zero JS runtime” pipelines that don’t want a Kit project at all

Light comparison (not a roast)

Need	Typical pick	SveltePress angle
Vue-native docs SSG	VitePress	Same content-first feel, SvelteKit underneath
Big React docs platform	Docusaurus	Lighter Kit-native path; versioning + i18n included
Stay in Svelte	—	First-class: Runes in MD, Kit adapters, typed themes

Try it / tell us what’s wrong

We’re especially hungry for feedback on:

First-hour DX (create → first deploy)
Versioning + i18n edge cases in real multi-product docs
Gaps vs your current VitePress/Docusaurus setup

👉 sveltepress.site · ⭐ GitHub

If you ship with it, a short “who’s using” note or issue is hugely helpful. Thanks for reading.

codsh 0.22.1 — /ship grill cards wrap long questions (DeepSeek terminal agent)

Dongsheng — Thu, 10 Sep 2026 09:40:33 +0000

DeepSeek-native terminal coding agent; /ship one sentence → verified code.

0.22.1: grill card wraps long questions fully (no 2-line ellipsis clip); sync dsh packages to 0.1.5-rc.1
Install: npm i -g @deepseek-ai/dsh codsh-cli && codsh
Links: GitHub · Docs · npm codsh-cli
Not a Claude Code env wrapper.

Feedback and a star are always appreciated.

DEV Community: Dongsheng

agent-usage NEW8: agents can torch a 5-hour window with no estimate

agent-usage 0.10.0: charts by agent, billing domain, and model

Real Bot: persistent AI teammates on your Mac (local multi-bot · MIT · BYO)

What you get

Status

codsh 0.23.0 — Mission Contract: `/ship` that won't silently drift

What changed in 0.23.0

Why this matters vs “just chat a plan”

What /ship builds (gallery)

Install (60 seconds)

Links

Agent Usage: One local dashboard for Codex, Claude Code, OpenCode, Grok & more

Quick start

Cost honesty

svelte5plus-calendar: Zero-dependency full calendar for Svelte 5

The problem

What it is

What you get

Quick start

Who it’s for

Who it’s not (yet) for

Light comparison (not a roast)

Try it / tell us what’s wrong

svelte-json-discovery: the discovery.js JSON struct view, as a Svelte 5 component

Install

Highlights

Monorepo layout

Credits & license

Call for feedback

Bring Claude Code and Codex into Feishu/Lark group chat — with permission cards

Why this exists

What it does

Quick start

Commands and caveats

SveltePress: Ship docs and blogs with SvelteKit — and Svelte 5 inside Markdown

The problem

What SveltePress is

What you get

Quickstart

Who it’s for

Who it’s not (yet) for

Light comparison (not a roast)

Try it / tell us what’s wrong

codsh 0.22.1 — /ship grill cards wrap long questions (DeepSeek terminal agent)

What `/ship` builds (gallery)