mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-11-15 02:49:33 +01:00
Claudia[bot]andClaude Opus 5.5
f06635512a
The update and kickstart prompts are textareas in the respawn settings and the schema accepts line breaks, so a saved config can hold several lines. Both steps went out through writeViaMux, which used to strip every `\n` and run the lines together. Since the mux now pastes multi-line text as one block, a multi-line respawn prompt would have gone out as a multi-line paste, and the check that re-presses a stranded Enter cannot recognise that paste in the composer. Respawn runs unattended, the same situation for which cron keeps rejecting multi-line prompts. singleLineRespawnPrompt() joins the lines with a space before the write; a single-line prompt is passed through unchanged. Respawn joins rather than rejects, so a multi-line config that was accepted before is still sent. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Changesets
Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works
with multi-package repos, or single-package repos to help you version and publish your code. You can find
the full documentation for it in the repository.
What is a changeset?
A changeset is a piece of information about changes made in a branch or commit. It holds three bits of information:
- What packages need to be released
- What semver bump type each package should receive (major / minor / patch)
- A summary of the changes
How do I create a changeset?
Run npx changeset or create a .md file in this directory with the following format:
---
"codeman": patch
---
Description of changes
The frontmatter specifies which package(s) to bump and the bump type. The body is the changelog entry.