Ebony-Vinyl/EAC-Desktop

This page introduces an external open-source repository. It is not an HDATF product.

What it does

EAC-Desktop is an application that packages DeepSeek Harness as a desktop workspace. It targets users who want conversations, project-file work, tool execution and plugin management around a project directory. Task requests, project files and model configuration feed a workflow in which Harness runs conversations and tools and the interface exposes file changes and results. Its documentation separates a Tauri window and tray shell, a Node sidecar for startup and environment orchestration, and a Harness agent kernel. Described capabilities include reviewing and reverting file changes, conversation compaction, model configuration and plugin-management entry points. Distribution packages prepare runtime resources, but model calls depend on the configured provider, while plugin activation and extra dependencies vary by package. The inspected environment adapter calls DPX environment creation, path and runtime-variable APIs to separate default data locations by release channel. This is not a filesystem sandbox: absolute-path access still depends on operating-system permissions, and third-party component licenses require separate checking.

License

MIT Permissive. Commercial use and changes are allowed if the copyright notice is kept.

More in this category

• homeassistant-ai/ha-mcp
  HA-MCP exposes Home Assistant management operations to AI clients through MCP, the protocol used to describe and invoke application tools. An AI client turns a user's request into structured tool arguments, and the server returns device states, histories, configuration data or operation results from the connected Home Assistant instance. Its tool registry covers device control as well as automation, script and dashboard editing and diagnosis from logs and execution traces. The inspected server initializes a FastMCP tool surface with visibility filters, optional search-based discovery and per-call enforcement rather than relying only on a model instruction to be careful. The recommended in-process integration requires a compatible Home Assistant installation, with the documented server setup floor at Home Assistant 2026.8.0, and an administrator account's access credential. Local and remote connection options differ, and a secret connection URL can itself be a credential that must be protected. Read-only connections hide and block writes, but the same credential can still access the normal endpoint, so this mode is not a separate credential-level permission boundary. Direct file and YAML editing are opt-in beta features, and backups and configuration checks do not eliminate semantic errors or the need for independent recovery access. Running the server locally does not guarantee local AI processing, because the selected MCP client can process Home Assistant data under its own privacy policy. This is a Home Assistant administration tool, not evidence of compatibility with industrial control systems or a guarantee that generated automation is safe.
• metadist/synaplan-desktop
  Synaplan Desktop connects a user's computer to a Synaplan workspace so that chat can lead to local file work. It takes requests, permitted files and installed Agent Skills and produces local artifacts such as reports, tables, calendar files and unsent email drafts. The native client uses Tauri and Vue and communicates with the server through pairing APIs and an Anthropic-compatible Messages gateway. A scoped pairing key is normally kept in the operating system's secret store. Local execution uses approved interpreters and structured program arguments, rejecting shells, network command-line tools and inline code. Skills needing unrestricted shell or network access do not run unchanged, and local Python or other required tools must already be available. The release is an unsigned preview for Windows, macOS and Linux, with signed public installers not yet published according to the README. Source inspection also shows that Windows timeout handling terminates the direct child rather than guaranteeing termination of its descendants, so isolation claims require separate validation.
• skaft-software/octet
  octet is a terminal coding agent for developers who want a native Rust runtime with cloud or local models. It takes prompts, source files and optional media and returns answers, file edits and command results. One process manages the agent loop, sessions, policies, persistence and terminal interface. Tools can be added through subprocess extensions, while MCP and subagents are optional integrations. Its first Pi-compatible release supports parts of the Pi extension ecosystem, but compatibility has documented gaps and arbitrary Pi transcripts are not imported. Sessions use append-only JSONL records with branches and checkpoints, and interrupted mutating calls are not automatically replayed. Model credentials and the chosen provider or local model must be prepared, and Windows support is still a preview. Full operating-system access is the default, and its approval-based safe mode is not a sandbox for commands or trusted extensions.
• darkmatter/nixmac
  nixmac is a macOS configuration manager that places an AI agent in front of Nix and nix-darwin settings. It is intended for Mac users who want to describe package or system-setting changes instead of editing Nix files directly. A natural-language request and an existing configuration become edited files, a change summary, and, through a separate apply path, a new system configuration. The agent reads files, searches packages and documentation, makes edits, and revises them using check results. The inspected implementation uses a dry-run Nix check during evolution, which does not perform the full package build described more loosely by the README. The apply path performs an actual build as the user and then activates the resulting system with administrative privileges. Git history and saved system paths support review and rollback, but restoring files and reactivating a system are separate operations. The documented environment is macOS with Nix flakes, nix-darwin configuration, and devenv, with models supplied through OpenRouter, OpenAI-compatible endpoints, or Ollama. Dry-run success does not establish successful activation or compliance with the user's intent, and a separate review button does not by itself prove an enforced backend approval boundary.
• agentclientprotocol/codex-acp
  This adapter connects Codex to editors and clients supporting ACP. It is a protocol server, not a separate language model or a complete development environment. It accepts text, images and workspace context, starts the Codex App Server, and returns replies, tool events, file changes and permission requests. Clients can select models, reasoning effort, sandbox modes and allowed user permission profiles. Native subagent sessions and some mid-turn capabilities require capability negotiation with the client. The npm package includes a compatible Codex dependency, but client launch configuration and Codex authentication remain separate prerequisites. Authentication supports ChatGPT login, API keys and negotiated custom gateways. Installation does not automatically configure every editor or establish a safe approval policy, and some permission-profile fields use an experimental schema.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.