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

# nut serve

> Launch the Coconut web interface

# `nut serve`

Start the Coconut web interface (Coconut Studio).

```bash theme={null}
nut serve [options]
```

## Overview

The `serve` command launches a local web server that provides the Coconut Studio interface. This gives you a graphical interface for managing your Coconut instance, including proposals, agents, code changes, and terminal sessions.

## Usage

**Start the web interface:**

```bash theme={null}
nut serve
```

The command will:

1. Start a local web server
2. Display the URL where Coconut Studio is accessible
3. Keep running until you stop it (Ctrl+C)

<Tip>
  By default, the web interface runs on `http://localhost:3000`. Check the terminal output for the exact URL if a different port is used.
</Tip>

## What You Can Do in Coconut Studio

Once the web interface is running, you can:

<CardGroup cols={2}>
  <Card title="Manage Proposals" icon="lightbulb">
    View, create, and edit change proposals
  </Card>

  <Card title="Configure Agents" icon="robot">
    Set up and manage AI agents
  </Card>

  <Card title="Review Code" icon="code">
    See code changes and diffs for proposals
  </Card>

  <Card title="Terminal Sessions" icon="terminal">
    Access integrated terminal sessions
  </Card>

  <Card title="Source Control" icon="git">
    Manage git operations and branches
  </Card>

  <Card title="Schedule Tasks" icon="clock">
    Configure scheduled jobs and automation
  </Card>
</CardGroup>

## Accessing the Interface

After running `nut serve`, open your web browser and navigate to the displayed URL (typically `http://localhost:3000`).

<Note>
  Keep the terminal window open while using Coconut Studio. Closing the terminal or pressing Ctrl+C will stop the server.
</Note>

## Common Options

While `nut serve` works without options in most cases, you may be able to specify:

* Custom port
* Network binding (localhost only vs. accessible from other devices)
* Debug mode

Run `nut serve --help` for available options.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Port already in use">
    If port 3000 is already in use, Coconut will typically try the next available port. Check the terminal output for the actual URL.
  </Accordion>

  <Accordion title="Can't access from browser">
    Make sure:

    * The `nut serve` command is still running
    * You're using the correct URL from the terminal output
    * Your firewall isn't blocking the connection
  </Accordion>
</AccordionGroup>