Water Code banner
pacificwater2 pacificwater2

Water Code

Development community

Description

A clean-room terminal coding agent built from Claude Code architecture research.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Water Code

Water Code is a clean-room terminal coding agent project built from architecture research on Claude Code, but intentionally re-designed as a simpler, zero-dependency Node MVP.

Detailed Chinese usage guide:

  • docs/user-manual-zh.md
  • docs/github-publish-guide.md
  • docs/github-release-v0.1.0.md

The first version focuses on the core loop:

  • CLI entrypoint
  • interactive REPL
  • session persistence
  • agent loop
  • tool registry
  • pluggable providers
  • explicit permission handling for dangerous tools

This repo does **not** try to clone every advanced subsystem on day one. It starts with a practical minimal core that can grow into a larger product.

Why this exists

The research showed that the most durable Claude Code idea is not any single hidden feature. It is the product skeleton:

`main -> commands/tools -> REPL -> query loop -> state/extensions`

Water Code uses that skeleton as inspiration while keeping the first implementation much smaller and easier to evolve.

MVP scope

Current MVP includes:

  • one-shot or interactive CLI
  • first-class slash commands
  • project context loading
  • git-aware project state and worktree awareness
  • formal JSON tool-calling protocol
  • diff preview and exact patch editing
  • structured tool result rendering
  • richer permission modes
  • approval history and remembered approvals for dangerous tools
  • project custom commands
  • project custom agents
  • project skills
  • project plugins
  • project-level WATER.md instructions
  • local MCP server loading
  • sequential multi-agent orchestration
  • background tasks
  • local HTTP bridge surface
  • bridge request timeouts and stream heartbeats
  • provider abstraction
  • planner provider for local testing
  • optional Anthropic-backed provider via environment variables
  • tools:
    • list_files
    • read_file
    • git_status
    • git_worktrees
    • preview_diff
    • patch_file
    • write_file
    • list_background_tasks
    • get_background_task
    • start_background_task