mirror of
https://github.com/OpenRouterTeam/spawn.git
synced 2026-04-29 20:39:29 +00:00
7abfb045af
Agent request: remove redundant name field (already in title), broaden traction criteria to include fork activity and venture funding. Cloud request: remove redundant name field (already in title), consolidate API docs and billing into Additional Context. New: CLI feature request template for spawn CLI improvements. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
51 lines
1.5 KiB
YAML
51 lines
1.5 KiB
YAML
name: CLI Feature Request
|
|
description: Suggest a new feature or improvement for the spawn CLI
|
|
title: "[CLI]: "
|
|
labels: ["cli", "enhancement", "needs-triage"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for the suggestion! Describe what you'd like the spawn CLI to do.
|
|
|
|
- type: textarea
|
|
id: description
|
|
attributes:
|
|
label: Feature Description
|
|
description: What should the CLI do? Be as specific as you can.
|
|
placeholder: |
|
|
spawn should support a `--dry-run` flag that shows what would
|
|
be provisioned without actually creating anything.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: use-case
|
|
attributes:
|
|
label: Use Case
|
|
description: Why do you need this? What problem does it solve?
|
|
placeholder: |
|
|
I want to preview costs before spinning up a server.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposed-ux
|
|
attributes:
|
|
label: Proposed UX
|
|
description: How would you expect to use this feature? Show example commands or workflows.
|
|
placeholder: |
|
|
$ spawn claude hetzner --dry-run
|
|
Would create: Hetzner CX22 in fsn1 (~$0.01/hr)
|
|
Run without --dry-run to proceed.
|
|
render: shell
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: additional
|
|
attributes:
|
|
label: Additional Context
|
|
description: Any other details, mockups, or references to similar tools
|
|
validations:
|
|
required: false
|