deepline-feedback

# Deepline Feedback ## Quick Start ```bash npm install -g deepline # Fallback for secure sandboxes: mkdir -p "$HOME/.local" && npm config set prefix "$HOME/.local" && export PATH="$HOME/.local/bin:$PATH" && npm install -g deepline --registry https://code.deepline.com/api/v2/npm/ deepline auth register --wait auto deepline auth wait --timeout 120 # completes Cowork/browser approval; no-op if already connected deepline auth status deepline -h ``` ## CLI resolution Run `deepline` when it is available. If the shell reports that command is missing, use `<workspace-root>/.deepline/runtime/bin/deepline` (or the npm-created `.cmd` shim on Windows). If neither exists, follow `https://code.deepline.com/SKILL.md` to set up Deepline. Send feedback or a bug report to the Deepline team. ## Steps 1. **Get feedback text.** Use the argument if provided (e.g. `/deepline-feedback the waterfall broke`). Otherwise ask the user. 2. **Confirm.** Use AskUserQuestion with a question like: > This report will include: > > - Your feedback: {feedback text} > - Environment info (auto-collected) > - Current session transcript > > Send this feedback? Options: "Send it" / "Cancel". 3. **If confirmed**, send the feedback text first: ```bash deepline feedback send "{feedback text}" --json ``` 4. **Send the session transcript.** Try the normal Claude transcript location first: ```bash deepline sessions send --current-session --json ``` If that reports ...