General-purpose agent in one static Go binary. ReAct loop, ACP server for IDEs, OpenAI-compatible REST API with embedded web UI, Telegram gateway, cron scheduler, long-term memory, context compaction, rules, skills, MCP. Distroless-ready, works with any OpenAI-compatible provider.
# Add to your Claude Code skills
git clone https://github.com/coddy-project/coddy-agentLast scanned: 7/22/2026
{
"issues": [
{
"file": "README.md",
"line": 99,
"type": "remote-install",
"message": "Install command (remote install script piped to a shell — review the source before running): \"curl -fsSL https://coddy.dev/install.sh | bash\"",
"severity": "low"
}
],
"status": "PASSED",
"scannedAt": "2026-07-22T06:27:22.427Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}coddy-agent is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by coddy-project. General-purpose agent in one static Go binary. ReAct loop, ACP server for IDEs, OpenAI-compatible REST API with embedded web UI, Telegram gateway, cron scheduler, long-term memory, context compaction, rules, skills, MCP. Distroless-ready, works with any OpenAI-compatible provider. It has 118 GitHub stars.
Yes. coddy-agent passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/coddy-project/coddy-agent" and add it to your Claude Code skills directory (see the Installation section above).
coddy-agent is primarily written in Go. It is open-source under coddy-project on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh coddy-agent against similar tools.
No comments yet. Be the first to share your thoughts!
| Desktop (1920×1080) | Mobile (390×844) |
|---|---|
![]() |
![]() |
| Chat | Mobile chat |
|---|---|
![]() |
![]() |
| History | Scheduler |
![]() |
![]() |
| Scheduler — job editor | Settings |
![]() |
![]() |
| Settings — Skills | Settings — Appearance |
![]() |
![]() |
Screenshots: desktop at 1920×1080, mobile at 390×844 from the embedded UI (coddy http + Vite dev). Spec and dev workflow: docs/ui.md, layout tokens: DESIGN.md.
Coddy is a distroless-friendly harness: drop it into minimal images (scratch, distroless, read-only workspaces) without a full OS shell. The same agent core is reachable from an IDE over ACP, a browser or any OpenAI client over HTTP, Telegram through the messenger gateway, and cron through the scheduler. The grep and glob filesystem tools use system ripgrep when available and fall back to built-in Go implementations when it is not. The harness layer (ACP RPC, sessions, prompts, providers) stays the same if you tighten the toolset or drive it from automation instead of an IDE. The design also targets container fleets - many Coddy instances in Docker (orchestrator-defined limits, read-only rootfs, mounted workspace) with full control of each container, similar in spirit to agent OS / swarm-style agents, not a single shared chat pool.
agent (full tool access) and plan (planning + text files only).cursor/rules/, .coddy/rules/, .claude/rules/, .codex/rules/, and nested **/AGENTS.md (agents.md) under the session cwd - see RulesSKILL.md packs from skills.dirs (defaults: ~/.agents/skills, ~/.coddy/skills, ${CWD}/.coddy/skills; later dirs override earlier) - see Skillsrun_command can run detached (background: true plus the model's own expected_seconds estimate); background_list / background_output / background_wait / background_stop collect the result later, a Tasks drawer in the UI shows what is still running with a status ticker, and the permission dialog can widen a grant to a whole program (curl, git status) so a batch of similar calls asks once - see Background tasks/compact [instructions] command and automatic summarization when the context reaches compaction.threshold_percent (default 80%) of the model's max_context_tokens; the last compaction.keep_recent_turns (default 2) user turns stay verbatim and the full transcript is preserved on disk - see Configurationmultimodal: true in the model config; assets saved to ~/.coddy/sessions/<id>/assets/ and injected into the agent context; file chips displayed in the user bubbleminimal/low/medium/high), mapped to OpenAI reasoning_effort or Anthropic extended-thinking budget_tokens; levels auto-detect from the model id and are configurable per model — see Configurationcoddy acp); pair it with editors or scripts that implement an ACP client (see Editor and IDE integration)ssh_run_command tool runs commands on remote hosts over pure-Go SSH (no external binary); authenticates via SSH agent (SSH_AUTH_SOCK) or ~/.ssh key files — see Configuration-tags gateway.telegram); per-user sessions, group isolation modes, admin ACL; extensible to Discord, Slack, etc. — see Messenger GatewayCoddy is an ACP server (coddy acp). Obsidian, VS Code, Zed, scripts, and the bundled coddy http UI are clients that share the same CODDY_HOME sessions when configured with the same home directory.
Configure clients with the absolute path to the binary rather than relying on PATH — some harnesses spawn the agent via cmd /c or sh -c without the user PATH (on Windows: %LOCALAPPDATA%\Programs\coddy\coddy.exe; see docs/install.md).
Protocol details: docs/acp-protocol.md. Harness examples: examples/acp/.
Linux / macOS - release binary plus ~/.coddy bootstrap:
curl -fsSL https://coddy.dev/install.sh | bash
Windows (PowerShell)
irm https://coddy.dev/install.ps1 | iex
Creates ~/.coddy/config.yaml from the release config.example.yaml when missing. Puts coddy on PATH (Unix: ~/.local/bin; Windows: %LOCALAPPDATA%\Programs\coddy). Full installer options: docs/install.md.
Windows. The binary lands at
%LOCALAPPDATA%\Programs\coddy\coddy.exe; config and sessions live under%USERPROFILE%\.coddy\(use$env:USERPROFILE, not$HOME). Runtime commands selectpwsh, then Windows PowerShell, thencmd.exe; Unix builds selectbash, thensh. The installing terminal does not see the updatedPATH— open a new one or refresh it in place. Details:docs/install.md.
Then set a provider key in ~/.coddy/config.yaml (or OPENAI_API_KEY in the environment) and run coddy http for the UI, or coddy acp for an editor client.
Docker - same full binary in ghcr.io/coddy-project/coddy-agent: docker compose up -d (see Docker).
Upgrade later with coddy update -y (How to update).
Prerequisites for building
go.mod (currently 1.25).http and ui (the Makefile runs ui-build for embedded assets).Install with Go (lean module default, no http / UI tags)
go install github.com/EvilFreelancer/coddy-agent/cmd/coddy@latest
For coddy http, the bundled SPA, scheduler, and memory, use a release binary (install script above) or build from source below.
**Recommended full binary from