manually inputting a CR or CRLF?

[orzechowskid]

I can't believe I'm asking this, but how do I input a CR or CRLF into the client? I often find it helpful to structure my thoughts by adding whitespace between paragraphs, or to enter bulleted or numbered lists. I've tried ctrl-Enter, shift-Enter, ^M, etc with no success.

I'm using urxvt on linux, though I am willing to try other terminals (including the ones built into emacs) if this problem is limited to my current toolchain.

thanks for any help you can provide!

[aa956]

I'm usually working around this (large prompt that's hard to edit in TUI) with full prompt of just @todo.md because of that.

todo.md in project root is usually where I collect exact prompt for the agent if it's over a single sentence:

@AGENTS.md

There's a bug in rendering this input file: `./samples/broken.yaml`.

Check the output `./samples/broken.svg` - text "SAMPLE123" is not visible when SVG is rendered.

Probably a Z-order problem?

If not, check the css file we're embedding into each svg.

I'm also adding @AGENTS.md on top each time because otherwise each subagent loop start like this:

$ python /project/script.py
# That's failed - let's try python3
$ python3 /project/script.py
# Imports failed, let's explore the project
$ find . $ -name "python*" -o -name "pyproject.toml" -o -name "*venv" | head -50
# Excellent - we have a venv
$ /project/.venv/bin/python3 /project/script.py
# Excellent, this runs
...

AGENTS.md has something like:

## Tools You Can Use
- **Install deps:** `uv sync`
- **Run CLI:** `uv run project samples/simple.yaml`
- **Test (all):** `uv run pytest`
- **Test (unit only):** `uv run pytest -m "not integration"`
- **Test (integration only):** `uv run pytest -m integration`
- **Lint:** `uv run ruff check .` (check), `uv run ruff check . --fix` (auto-fix)
- **Lint Markdown:** `uv run pymarkdown scan docs/ README.md`
- **Format:** `uv run ruff format .` (auto-format), `uv run ruff format . --check` (check only)
- **Type check:** `uv run mypy .`
- **Build:** `uv build`

## Bash Command Convention
When running commands via the `bash` tool, **always use the `cwd` parameter** to set the working directory instead of prefixing commands with `cd`.

- ✅ **Good:** `bash(command="uv run ruff check .", cwd="/path/to/project")`
- ❌ **Bad:** `bash(command="cd /path/to/project && uv run ruff check .")`

[mlhher]

@file works because this is a training artifact of the model (Qwen?). We (late, the harness) don't do anything extra here.
This might be (or not) bundled with the image input. Image input does seem to work already I just have quite a lot to do right now so I don't really have a free moment to finish, test, clean, optimize, bundle up and publish. I am now seeing that a laptop might be quite helpful lol.

The commit from yesterday does contain newline (using Alt+Enter, it also contains some more keybindings noted in the Quickstart Guide) but it is not yet bundled into a release.

Also a sidenote for Emacs: I would not try using Late with Emacs terminals. The inbuilt ones were not a great experience for me and while eat seemed to more or less work it still had some weird quirks from what I remember. vterm was better than the inbuilt ones but also not really great (pgtk wayland).

[aa956]

Yes, Qwen 3.6.

Basically equivalent to plain text instruction like:
Read .agents/AGENTS.md. Review the state machine in function(). ...

[mlhher]

Alt+Enter works now was released in 1.2.3. Please get the new binary (or use homebrew).