# Text lines chunk

`text-lines-chunk` · version 1.0.0 · Text · free, no key needed

Split parsed lines into consecutive chunks of size lines each.

**Use when you need to: text lines chunk · chunk lines · split lines by size.**

## Supported

- text lines chunk
- chunk lines
- split lines by size

## Not supported

- overlap chunks
- bytes chunk
- stream

## Behavior

- Split on CR LF, LF, or CR. Do not treat other Unicode separators as line breaks.
- A trailing terminator does not create an extra empty line.
- Empty document -> zero lines, trailing_terminator false.
- A document that is only a terminator -> one empty line, trailing_terminator true.
- A document with no terminator -> last line kept, trailing_terminator false.
- Preserve empty lines in the middle.
- Output reconstruction uses LF. If the result has at least one line, append a trailing LF iff the selected window includes the original trailing terminator or includes a line that was followed by a separator in the source.
- No trimming, case folding, Unicode normalization, or locale rules.
- size is a JSON integer, 1 <= size <= max_lines.
- Chunks are consecutive, last chunk may be shorter.
- Empty input -> chunks [].
- If the number of chunks would exceed 512, reject.
- Each chunk string uses LF reconstruction; a non-final chunk always has a trailing LF if it is non-empty; the final chunk follows original trailing-terminator rules.

## Input

- `text` (string, required): max length 256000
- `size` (integer, required): min 1; max 10000

## Output

- `chunks` (array of string, required): max items 512
- `lines_in` (integer, required)
- `chunk_count` (integer, required)

## Limits

- max input bytes: 256000
- max lines: 10000
- max chunks: 512

## Example

Request input:

```json
{
  "text": "a\nb\nc\n",
  "size": 2
}
```

Response:

```json
{
  "result": {
    "chunks": [
      "a\nb\n",
      "c\n"
    ],
    "lines_in": 3,
    "chunk_count": 2
  }
}
```

## How to call it

### MCP

Connect `https://computefirst.net/mcp` ([setup](/docs#connect)), then call `execute` with:

```json
{
  "id": "text-lines-chunk",
  "version": "1.0.0",
  "input": {
    "text": "a\nb\nc\n",
    "size": 2
  }
}
```

### HTTP (no key)

```sh
curl -X POST https://computefirst.net/v1/tools/text-lines-chunk/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"text":"a\nb\nc\n","size":2}'
```

The machine-readable contract is at [/v1/tools/text-lines-chunk/versions/1.0.0](/v1/tools/text-lines-chunk/versions/1.0.0).

### CLI

```sh
node cli.mjs run text-lines-chunk 1.0.0 --input input.json --base-url https://computefirst.net
```

Get the client at [/clients/cli/](/clients/cli/).

## Related tools

- [Text line diff](/tools/text-line-diff): Diff two texts as line records, preserving each line terminator.
- [Text conflict parse](/tools/text-conflict-parse): Parse merge or diff3 conflict-marker text into ordered text and conflict parts.
- [Text count](/tools/text-count): Count Unicode code points, UTF-16 code units, UTF-8 bytes, and lines.
- [Text lines count](/tools/text-lines-count): Count exact line multiplicities in first-seen order.
- [Text lines difference](/tools/text-lines-difference): Set difference a minus b using exact line equality.
- [Text lines head](/tools/text-lines-head): Return the first n parsed lines with LF reconstruction.