---
title: "overlane task export"
description: "Write the project's imported work back out in the TASKS.md layout"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.overlane.app/llms.txt
> Use this file to discover all available pages before exploring further.

# overlane task export

{/* Generated by apps/docs/scripts/generate.mjs (CLI pages from the command registry in packages/cli). Do not edit; run `pnpm --filter @overlane/docs gen`. */}

Prints the project's issues in the TASKS.md layout on stdout, so `overlane task export --format tasks-md \> TASKS.md` reproduces an imported file line for line. Line endings are LF and the file ends with one newline; issues made in Overlane after the import are listed at the end under their own heading.

## Usage

```sh
overlane task export --format tasks-md
```

## Flags

| Flag | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `--format` | one of `tasks-md` | yes |  | The layout to write |

## Examples

```sh
overlane task export --format tasks-md > TASKS.md
```

## Behavior

- Effect: `read` (changes nothing).
- Needs credentials: yes. Uses the network: yes.
- Supports `--dry-run`: no. Accepts `--force`: no.
- Machine-readable description: `overlane schema task export`.

## Result

With `--json` (the default when stdout is not a terminal) the command prints this JSON Schema's shape on stdout.

```json
{
  "type": "object",
  "properties": {
    "format": {
      "type": "string",
      "const": "tasks-md"
    },
    "imported": {
      "type": "number"
    },
    "other": {
      "type": "number"
    },
    "content": {
      "type": "string"
    }
  },
  "required": [
    "format",
    "imported",
    "other",
    "content"
  ],
  "additionalProperties": false
}
```

See [exit codes](/cli/#exit-codes) for the status the process returns.

Source: https://docs.overlane.app/cli/task-export/index.mdx