The 1.0 release candidate isn't on npm, so what does installing actually involve?

A source checkout: clone the repo, run pnpm install, then cargo build --locked --release -p smithers-ffi --bin smithers-jj-export, and put node_modules/.bin on your PATH. From your project directory you then run smthrs init change and smthrs flow start change.

Which platforms does the local CLI actually support?

The README states the release candidate's required platform is Linux with Node 26.4.0 and points at a support matrix page. macOS and Windows are not listed as supported for local execution, so treat Linux as the only documented target.

Do I need model credentials before the first run?

Yes. You edit the scaffolded flow and configure the credential its model: field requires before launching, so the flow is not usable until that key is in place. The README does not document which providers or models are supported.

How do I see what it changed before it touches my repository?

In the browser version you can explore the repository files, ask for work in chat, and inspect runs and changes inside the conversation. You sign in with GitHub at the point you are ready to contribute.

What does Smithers actually do to a codebase?

It maintains your codebase by turning issues into reviewed, tested changes, and when enabled it keeps the project wiki current. Flows defined beside your code decide how each run behaves.

How do I start a change flow?

From your project directory, run smthrs init change and then smthrs flow start change. Before launching, edit the scaffolded flow and configure the credential that its model: field requires.

Where is the documentation and the build API reference?

Tutorials, guides and the full reference are at smithers.sh/docs. The top-level build API is covered by a cheat sheet at packages/smithers/build/targets/docs/reference/cheat-sheet.md, one file of TypeScript examples spanning the whole Smithers.* surface.

CommunityJev Integrations & Adapters

Smithers

Smithers turns issues into reviewed, tested changes through flows defined beside your code, with an optional step that keeps the project wiki current. The 1.0 release candidate runs from a source checkout.

See highlights

Open github.com

Stars: 431
Language: TypeScript
License: MIT
Published by: Community
Author: smithersai
Last verified: Oct 2026

smithersai/smithers

Organization repository on GitHub

View on GitHub

Smithers is an agentic workflow framework for defining workflows in simple TypeScript configuration files and executing them quickly, durably, and reliably

Forks: 51
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

About this project

███████╗███╗ ███╗██╗████████╗██╗ ██╗███████╗██████╗ ███████╗ ██╔════╝████╗ ████║██║╚══██╔══╝██║ ██║██╔════╝██╔══██╗██╔════╝ ███████╗██╔████╔██║██║ ██║ ███████║█████╗ ██████╔╝███████╗ ╚════██║██║╚██╔╝██║██║ ██║ ██╔══██║██╔══╝ ██╔══██╗╚════██║ ███████║██║ ╚═╝ ██║██║ ██║ ██║ ██║███████╗██║ ██║███████║ ╚══════╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝╚══════╝. Smithers maintains your codebase. It turns issues into reviewed, tested changes and, when enabled, keeps the project wiki current. Flows beside your code define how.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest

Works forJev for Classification Jev for Tool calling

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

Flows written next to the source define how an issue becomes a reviewed, tested change.
Keeping the project wiki current is an optional part of the same maintenance loop.
Runs in the browser against the hosted repository, or locally with smthrs init change and smthrs flow start change.
The 1.0 release candidate is not on npm; installing needs pnpm install plus a cargo build of the smithers-ffi jj-export binary.

Watch out

The README is short and does not enumerate flow types, model providers, or what the wiki step actually covers, so scope has to come from the docs site. The 1.0 release candidate is not on npm and the required platform is Linux with Node 26.4.0. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

system-one

Provider-neutral TypeScript runtime for System One decisions: write choice, noul, and score code once, then run it on TypeSafe Jev, local Reflex, any compatible /v1/systemone endpoint, or a custom provider.

Jev Integrations & Adapters#community#jevbest#catalog-import

Community

iamaamir/system-oneTypeScript

algal

Language and VM for agent programs that wait for approval, survive restarts, and replay portable receipts without recalling the model.

Jev Integrations & Adapters#community#jevbest#catalog-import

Community

hraness/algalTypeScript

hiep-paseo-plugin

Fifteen independent local plugins for the Paseo desktop app, two of which use Jev: an evaluator exposed to Codex and Claude agents over MCP, and an orchestrator that routes a task to one model profile and effort level.

Jev Integrations & Adapters#community#jevbest#catalog-import

Community

HiepPP/hiep-paseo-pluginTypeScript

Eliza

19.6k

Open-source TypeScript agentic operating system: a core runtime, app for web and mobile, CLI, cloud services and first-party plugins. The directory's curated summary reports it integrates TypeSafe System One decision services for sub-100ms intent classification, action dispatching and confidence-gated tool execution.

Jev Integrations & Adapters#community#agents#framework

Community

elizaOS/elizaTypeScript

learn-agent-architecture

1.1k

A section-by-section guide to agent harnesses - loop, tool runtime, permissions, hooks, subagents, skills, memory, background work - using Claude Code, mini-swe-agent, Hermes Agent, and deepseek-harness as worked examples.

Jev Integrations & Adapters#community#jevbest

Community