# RENDER_LOCAL_DEV_URL=http://localhost:8121
```

**Render API**

If your app uses the Render API directly to run tasks, swap out the base URL you use for task-related endpoints with your local task server's URL.

Here's a Node.js example:

```js
const TASKS_BASE_URL = process.env.RENDER_TASKS_URL || 'https://api.render.com'
```

In this example, you would set the `RENDER_TASKS_URL` environment variable to your local task server URL (e.g., `http://localhost:8120`) to use it for development.

Note that the local task server _only_ simulates task-related endpoints. Other Render API endpoints are not supported.

### In the Render CLI

1. With your [local task server running](#starting-the-task-server), run the following command:

   ```shell
   render ea tasks list --local
   ```

   **Don't forget the `--local` flag!** Otherwise, the CLI will list tasks from your deployed workflow services.

   The CLI opens an interactive menu of your locally registered tasks:

   [img]

2. Select a task and press **Enter**, then select the `run` command.

   The CLI prompts you to provide the task's input arguments as a JSON array:

   [img]

   If you task takes zero arguments, provide an empty list, `[]`.

3. Provide your desired arguments and press **Enter**. The CLI kicks off your task with a request to your local task server and begins tailing its logs.

   You can remain in this view to view live logs from your task run.

4. Press **Esc** to navigate back up to the list of commands for your task. This time select the `runs` command.

   The CLI opens an interactive menu of the task's local runs:

   [img]

5. Select a run and press **Enter**, then select the `results` command.

   The CLI opens a view of the run's results:

   [img]

## Local-only considerations

- Logs and results for local task runs are stored in memory by the local task server.
  - This data is lost when the server shuts down.
  - This data is retained indefinitely as long as the server is running. This can lead to high memory usage over time.
  - If you trigger a high volume of local task runs, we recommend periodically restarting your local task server to free up memory.
- Identifiers for local tasks and runs are randomly generated UUIDs.
  - The identifier for a given task differs each time you run the local task server.
  - Local identifiers do not correspond to any values in your deployed workflow services.