feat: cog playground

[anish-sahoo]

Cog Playground

A browser-based playground UI for testing Cog models locally, served by a Go HTTP server embedded in the Cog CLI.

Stack PRs

1. 1. Add Go playground server and handlers #3109
2. 2. Add playground frontend scaffold and early CI #3108
3. 3. Add core playground types and utilities #3114
4. 4. Add shared playground UI and JSON editor #3110
5. 5. Add Cog playground API client #3106
6. 6. Add playground connection feature #3105
7. 7. Add playground input controls and validation #3111
8. 8. Add playground prediction controls and output #3107
9. 9. Wire up Cog playground and documentation #3113
10. 10. Compose playground app and add browser e2e #3112

[ask-bonk]

I found one critical issue in this PR:

newPlaygroundCommand() is never registered in pkg/cli/root.go.

The cog playground command is fully implemented in pkg/cli/playground.go, but it is never added to the root command, so users will see ``unknown command" when they run cog playground.

Fix:

// pkg/cli/root.go
rootCmd.AddCommand(
    newBuildCommand(),
    newDebugCommand(),
    newDoctorCommand(),
    newInitCommand(),
    newLoginCommand(),
    newRunCommand(),
    newPredictCommand(),
    newPushCommand(),
    newExecCommand(),
    newServeCommand(),
    newTrainCommand(),
    newWeightsCommand(),
    newPlaygroundCommand(),  // <-- add this
)

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds a cog playground command with a browser-based UI for interacting with running Cog models, plus the frontend scaffold, CI integration, and build pipeline changes. Overall the implementation is solid — the Go server has good security boundaries (loopback-only UI, webhook exemption for containers, CORS-safe proxying, CSP headers) and thorough test coverage.

I found one critical issue that prevents the command from being usable at all:

newPlaygroundCommand() is never registered in pkg/cli/root.go.

The command is fully implemented in pkg/cli/playground.go but is never added to rootCmd.AddCommand(), so cog playground will return "unknown command".

Posted the fix as a PR comment: #3115 (comment)

github run

[ask-bonk]

I found one critical issue in this PR:

newPlaygroundCommand() is never registered in pkg/cli/root.go.

The cog playground command is fully implemented in pkg/cli/playground.go, but it is never added to the root command, so users will see "unknown command" when they run cog playground.

Fix:

// pkg/cli/root.go
rootCmd.AddCommand(
    newBuildCommand(),
    newDebugCommand(),
    newDoctorCommand(),
    newInitCommand(),
    newLoginCommand(),
    newRunCommand(),
    newPredictCommand(),
    newPushCommand(),
    newExecCommand(),
    newServeCommand(),
    newTrainCommand(),
    newWeightsCommand(),
    newPlaygroundCommand(),  // <-- add this
)

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds a cog playground command with a browser-based UI for interacting with running Cog models, plus the frontend scaffold, CI integration, and build pipeline changes. The Go server has good security boundaries (loopback-only UI, webhook exemption for containers, CORS-safe proxying, CSP headers) and thorough test coverage.

I found one critical issue that prevents the command from being usable at all:

newPlaygroundCommand() is never registered in pkg/cli/root.go.

The command is fully implemented in pkg/cli/playground.go but is never added to rootCmd.AddCommand(), so cog playground will return "unknown command".

Posted the fix as a PR comment: #3115 (comment)

github run