accomplish - Moses Yebei

The Problem

Teams that rely on desktop AI assistants often have to trust cloud‑hosted services that keep files and prompts on external servers. When data residency, API‑key control, or offline operation matter, there is no ready‑to‑run, open‑source desktop agent that can orchestrate file moves, document generation, and browser automation while keeping every request on the local machine.

What This Does

Accomplish™ is a self‑contained Electron app that runs on macOS and Windows. The core runtime lives under apps/desktop/src/main/ (e.g. index.ts, ipc/handlers.ts) and exposes IPC endpoints to the renderer UI (src/renderer/). Skills are defined in src/main/skills/ and invoked from the UI components in src/renderer/components/.

File management – src/main/services/* contains speechToText.ts and summarizer.ts; the actual move/rename logic lives in src/main/opencode/* and is triggered via IPC calls from the renderer.
Document creation – UI components such as renderer/pages/Execution.tsx call the OpenCodeAdapter (found in packages/agent-core/src/internal/classes/OpenCodeAdapter.ts) which forwards prompts to the selected provider (OpenAI, Anthropic, Ollama, etc.) and returns generated text.
Provider flexibility – Provider modules are under src/main/providers/ (e.g. vertex.ts) and are selected by the settings UI (renderer/components/settings/shared/). API keys are read from the user‑supplied JSON config loaded by src/main/config.ts.

How It Is Wired

Entry point – Electron boots via apps/desktop/src/main/index.ts.
IPC bootstrap – src/main/ipc/handlers.ts registers handlers defined in src/main/ipc/handlers/*. Each handler validates input (validation.ts) and forwards to service or skill code.
Skill dispatch – src/main/skills/SkillsManager.ts loads skill definitions from bundled-skills/ and routes UI requests (e.g., “run skill X”) to the appropriate adapter.
Provider call – The adapter (OpenCodeAdapter.ts) imports the hub module packages/agent-core/src/common/types/provider.ts (the most‑connected hub, 15 dependents) and invokes the selected provider implementation.
Result flow – Responses travel back over IPC to the renderer, where components like Execution.tsx update state and write logs via src/main/logging/*.

The import graph shows 354 internal modules with 0 circular dependencies. The most‑connected hub (provider.ts) has a low instability score (0.06) but a high blast radius; any change there ripples to 15 downstream modules.

How To Use It

# Clone the repo
git clone https://github.com/moses-y/accomplish
cd accomplish

# Install dependencies with pnpm (lockfile present)
pnpm install --frozen-lockfile

# Build the Electron app (script defined in apps/desktop/package.json)
pnpm --filter ./apps/desktop run build   # or `pnpm run dev` for hot reload

# Run the built binary (macOS example)
./apps/desktop/dist/Accomplish.app/Contents/MacOS/Accomplish

Configuration – API keys are expected in a JSON file loaded by src/main/config.ts. The repo ships a placeholder apps/desktop/e2e/provider-tests/secrets.example.json; replace it with real credentials before first run. No .env template is provided, so developers must create the config manually.

Real‑World Use

A marketing team can drop a folder of raw copy into a watched directory. Accomplish detects new files via the FileWatcher (wired through src/main/opencode/auth-browser.ts), triggers the “Document Writing” skill, and writes polished drafts back to the folder—all without any network request leaving the workstation.

Code Health & Issues

Measured findings (static analysis)

High – Deep nesting (8 files, e.g., renderer/pages/Execution.tsx): indentation depth 8, hard to follow.
High – Oversized files (9 files, e.g., OpenCodeAdapter.ts 691 lines).
High – Duplicated code blocks (repeated 6‑line snippets across 110 files).
Medium – Hub module (3 files under common/types/provider*): 15 dependents, high churn risk.
Medium – High branching density (10 files, e.g., waiting-detection.ts): >18 branches in <50 lines.

Code‑health audit (GitHub Actions & Docker)

High – Pin third‑party actions to commit SHA (.github/workflows/*).
High – CI never runs tests (4 workflows lack a test step).
Medium – Least‑privilege GITHUB_TOKEN missing in ci.yml.
Medium – Use lockfile in CI (npm install instead of npm ci).
Medium – Pin Docker base image by digest (apps/desktop/e2e/docker/Dockerfile).
Medium – No dependency vulnerability scan in CI.
Medium – Checkout persists token; should set persist-credentials: false.
Medium – Run container as non‑root (no USER directive).
Medium – Postinstall script executes untrusted code; consider disabling scripts in CI.
Low – No job timeout on pr-preview-release.yml.

Other hygiene – Tests exist (71 files) but are not invoked by CI; a secret‑shaped example file is committed; licence (MIT) present; lockfile (pnpm-lock.yaml) present.

The Bottom Line

Accomplish delivers a functional, locally‑run AI desktop agent with a clear separation between UI, IPC, and provider adapters. The codebase is sizeable and suffers from deep nesting, oversized modules, and duplicated logic, which will increase maintenance cost. CI gaps and Docker hardening issues should be addressed before production use. It is suitable for teams that need full data control and are prepared to invest in refactoring and CI hardening.

What the analyser found

Deployment readiness

6/7

Container image
CI pipeline
Lockfile committed
Test suite
README
License
No committed secrets

Composition

521 files

TypeScript279
TSX79
Markdown32
JSON30
YAML11
Shell5

ReactTailwindDocker

Module dependencies

The 10 most depended-upon modules of 354, from static import analysis. Red outline marks a module in an import cycle.

graph LR n0_re_src_common_types_provider["provider"] n1_ommon_types_providerSettings["providerSettings"] n2_t_core_src_common_types_task["task"] n3__src_common_types_permission["permission"] n4_s_agent_core_src_utils_fetch["fetch"] n5_onents_settings_shared_index["index"] n6_apps_desktop_e2e_pages_index["index"] n7_ore_src_common_types_logging["logging"] n8_re_src_common_types_opencode["opencode"] n9_t_core_src_common_types_todo["todo"] n0_re_src_common_types_provider --> n1_ommon_types_providerSettings

Findings

LowSecret-shaped paths present; the code-health audit confirms or clears them apps/desktop/e2e/provider-tests/secrets.example.json

What would stop me shipping this

Ranked by severity × confidence × production reach. Reach is the honest discriminator across a collection that is mostly other people's code: the same finding matters more in something that ships.

high2

medium7

low2

Pin third-party GitHub Actions to a commit SHAhigh3 occurrences

.github/workflows

pnpm/action-setup@v4, changesets/action@v1, softprops/action-gh-release@v2

A tag can be moved, so the action running with your token and secrets is whatever its owner last pushed; this is how tj-actions/changed-files leaked secrets from thousands of repos.

Fix: Replace each @vN with the 40-character commit SHA, keep # vN as a comment, and let Dependabot bump the SHAs.

Make CI invoke the test suite it hashigh71 occurrences

.github/workflows

71 test files, no test command in the 4 workflows read

A green check that never executed an assertion is worse than no check, because reviewers trust it.

Fix: Add a test step to the existing workflow rather than a new workflow.

Declare least-privilege permissions for GITHUB_TOKENmedium

.github/workflows/ci.yml

1 workflow(s) declare no permissions

With no declaration the token inherits the repository default, so any injected step can push commits or mint releases from inside your own CI.

Fix: Add permissions: contents: read at the top of the workflow and widen per job only where needed.

Install from the lockfile in CImedium

.github/workflows

npm install with a committed package-lock.json

A fresh resolution in CI means the tested dependency set is not the locked one, so the failure only appears after merge.

Fix: Use npm ci, yarn install --immutable, or pnpm install --frozen-lockfile.

Pin the container base image by digestmedium

apps/desktop/e2e/docker/Dockerfile

mcr.microsoft.com/playwright:v1.49.1-noble

An untagged or mutable base means today's build and last month's contain different libc and a different CVE set, with no record of which shipped.

Fix: Use image:tag@sha256:<digest> and enable Dependabot's docker ecosystem.

Gate pull requests on a dependency vulnerability scanmedium

.github/workflows

no dependency scan in CI

This is the one gate that would catch a known-vulnerable package before it reaches a build, and no repository in the sample had it.

Fix: Add dependency-review-action on pull_request, or osv-scanner on push and a schedule.

Set persist-credentials: false on checkoutmedium

.github/workflows/ci.yml

checkout keeps the token, then dependencies are installed

The token stays in .git/config for every later step, so a malicious postinstall script reads a pushable credential without one ever being passed to it.

Fix: Add with: persist-credentials: false, and pass an explicit token only to the step that pushes.

Add a non-root USER to the imagemedium

apps/desktop/e2e/docker/Dockerfile

CMD or ENTRYPOINT with no USER directive

A process running as root in the container is root against every mounted volume, and it turns any container escape or writable-mount mistake from a contained problem into a host one.

Fix: Create an unprivileged user, chown what it needs, and end the Dockerfile with USER.

Review the install lifecycle script and disable scripts in CImedium

package.json

postinstall

Install scripts are the execution vector for every npm compromise from event-stream onward, and a postinstall that fetches a binary makes the build depend on a URL nobody reviews.

Fix: Move the work into an explicit build step, or set ignore-scripts in CI and run it by name.

Set timeout-minutes on the workflow jobslow3 occurrences

.github/workflows/pr-preview-release.yml

3 workflow(s) declare no job timeout

A wedged step runs to the six-hour platform default, which on a two-hourly schedule means three runs overlap behind it.

Fix: Add timeout-minutes with a realistic bound to each job.

Add the repository convention files this project lackslow3 occurrences

missing .editorconfig, .gitattributes, a formatter config

Without them one contributor's editor writes tabs into a Python file, a shell script commits with CRLF and fails in the container, and a notebook diff is unreviewable.

Fix: Add .editorconfig, .gitattributes with text=auto eol=lf, and a formatter config.

Checked deterministically against the repository tree and a bounded set of its files: committed credentials, unpinned actions and base images, missing lockfiles and update bots, workflows that discard failures, published advisories against the declared dependencies, runtime configuration, licensing and notebook reproducibility. No language model is involved in this section.