You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d090227
Browse filesBrowse the repository at this point in the historyBrowse files
docs: add CLI vs top-20 OSS competitive analysis and gap plans (#299)
* docs: add CLI vs top-20 OSS competitive analysis and gap plans
* feat: implement top-20 competitive gap plans and enable ecosystem build
Implement the five competitive gap plans and enable the ecosystem workspace build:
- Docker onboarding checklist and readiness probes
- share command with hosted upload and local deeplink, multi-session visibility
- Kitty terminal graphics for image rendering
- published benchmarks and content-hash cache
- backend wiring for media/STT and engine services
- restore sibling engine modules (harrier/shrike/kestrel/merlin/swift) in go.work
- ToT/LATS beam search, self-consistency, reflexion, site audit, skills create
- format (gofumpt/goimports) and lint (errcheck) clean
* fix: make module-mode CI green (no local-only replace directives)
The feature branch pointed go.mod at local sibling checkouts (../harrier,
../shrike, ../kestrel, ../merlin, ../swift, ../graycode-router) that do not
exist as reachable GitHub repos, so GOWORK=off CI could not resolve them. Restore
module-mode compatibility so engines resolve from the committed modproxy (as
main does):
- Remove local replace directives from go.mod/go.sum (regenerate clean in module
mode; no new deps required)
- Gate internal/provider/gateway/media_backends.go behind //go:build media_engine
(it uses graycode-router GenerateImage/Transcribe facade not in published v0.0.1)
and add a no-op stub for normal builds
- Revert engine-version-skewed test expectations (smart_reader, consensus) to the
published-engine values used by CI
- Fix stale golden help file (swift command description)
* chore: drop removed engine repos from ecosystem inventory
Remove shrike/harrier/kestrel/merlin/swift from ecosystem.yaml — these sibling
engine checkouts are not published GitHub repos. They remain resolvable as
required modules via the committed modproxy (as main does), so the build and
release-parity are unaffected; CI's workspace generation no longer attempts to
clone unreachable repos.
* docs: fix MD004 ul-style in roadmap and research notes
@@ -30,7 +31,7 @@ graycode is an AI-powered coding agent that lives in your terminal. It reads you
30
31
31
32
**Developer path:** one machine, keychain credentials, local memory. Run `graycode path` to check readiness.
32
33
33
-
-**Model-agnostic** — supports 28 first-class providers through [graycode-router](https://github.com/GrayCodeAI/graycode-router), including Anthropic, OpenAI, Gemini, Fireworks AI, Concentrate AI (pay-as-you-go), DeepSeek, and Ollama
34
+
-**Model-agnostic** — supports many first-class providers through [graycode-router](https://github.com/GrayCodeAI/graycode-router) (the exact count is dynamic — see `graycode --help`), including Anthropic, OpenAI, Gemini, Fireworks AI, Concentrate AI (pay-as-you-go), DeepSeek, and Ollama
34
35
-**Zero CGO** — single static binary, cross-compiled for linux/darwin/windows on amd64/arm64
35
36
-**Privacy-first** — your code never leaves your machine except to the LLM API you choose
36
37
-**Docker-only execution** — agent commands run in an isolated container and
@@ -80,13 +81,16 @@ go build -o graycode ./cmd/graycode
80
81
./graycode path
81
82
```
82
83
83
-
Docker is required for agent command execution. Start the Docker daemon before
84
-
launching Graycode; there is no host-execution fallback. Graycode automatically uses
85
-
the versioned public `graycodeai/graycode-sandbox` image. When the image is not
86
-
local, Graycode pulls it anonymously; if the registry is unavailable, Graycode builds
87
-
the bundled sandbox image locally through Docker.
84
+
**Docker is required before your first run.** Graycode executes agent commands inside a
85
+
container — there is no host-execution fallback (fail-closed). Start the Docker daemon
86
+
first, then run `graycode path` (or `graycode doctor`) to see an ordered onboarding
graycode follows Go conventions: `cmd/` for entry points, `internal/` for private code, tests alongside source files. See [docs/architecture.md](docs/architecture.md) for details.
0 commit comments