Agent does't reply in Android app from agent-starter-android repo

Getting Started
1

Hello,

Following the instructions to run the agent-starter-android app doesn’t seem to work. The agent is not replying and no errors are shown in the console.

Issue Reproduction Steps

  1. Sign up on LiveKit and create project

  2. Enable token server in project settings on LiveKit Cloud

  3. Create new agent in web dashboard using Create in browser using Agent Builder button and deploy

  4. Copy Token server sandboxId from project settings on LiveKit Cloud

  5. Run the command after replacing <token_server_sandbox_id> with the one from the previous step

    lk app create --template agent-starter-android --sandbox <token_server_sandbox_id>

  6. Open project in Android Studio

  7. Sync Gradle files

  8. Build and run the app

  9. Tap on start call and allow mic access

  10. No greeting from agent, no error in the console, chatting with the agent doesn’t result in the agent replying.

I sporadically see some sessions being created with some delay in my dashboard but they’re closed.

image
image2840×240 26.7 KB

I also followed the instructions in https://github.com/livekit-examples/agent-starter-python to deploy an agent but the Android app still doesn’t reply after deploying the agent via CLI. So, the issue doesn’t seem related to deploying agents on the dashboard.

Am I missing a step? How to fix this issue?

2

Two things:

I believe these two steps should resolve your issue, but let me know. I haven’t tried the Android starter with our new sandbox TokenSource

3

Thank you! I indeed had a deployed agent and deleted it. (Side note: This is also the same issue as the one reported on GitHub.)

[…] the agent needs to be dispatched to the same room as the Android participant. […]

How can I ensure that my agent is in all rooms that are created in my application? I would like to build an app where participants can speak with the agent 1:1—i.e., each room should only include the participant and the agent. This seems to be solved by including the agentName in the rememberSession constructor.

[…] it doesn’t specify the agent name (which must match the name of the agent you created)

Exactly that was my question: How does LiveKit (for Android) know which agent to use?

Thank you for the hint about the missing parameter. I edited these lines as follows where agentName is defined with the name of my deployed agent:

val session = rememberSession(
        tokenSource = viewModel.tokenSource,
        options = SessionOptions(
            room = viewModel.room,
+           tokenRequestOptions = TokenRequestOptions(agentName = "Sage-1b7b")
        )
    )

It works with warnings when I using an agent deployed via dashboard, but it didn’t work when I used an agent deployed via CLI.

Dashboard-deployed Agent

Warnings in dashboard-deployed agent shown in the app:

Received byte stream for topic "lk.agent.session", but no handler was found. Ignoring.

The following error is shown when hanging up the call with the agent:

Error sending metrics:
io.livekit.android.room.RoomException$ConnectException: Publisher isn't setup yet! Is room not connected?!
at io.livekit.android.room.RTCEngine.ensurePublisherConnected(RTCEngine.kt:805)
...

These are the logs above as shown in Android Studio (including additional info):

image
image1920×1078 664 KB

CLI-deployed Agent

Error in CLI-deployed agent is “Missing configuration” shown in the terminal with lk agent logs:

{"message": "process initialized", "level": "INFO", "name": "livekit.agents", "pid": 126, "elapsed_time": 0.6, "timestamp": "2026-04-11T09:15:17.928538+00:00"}
{"message": "Missing configuration", "level": "ERROR", "name": "livekit.plugins.ai_coustics", "room": "sbx-2reup2-irxC839KnguXhA9bopXo28", "pid": 84, "job_id": "AJ_o4hYQxWY8Rox", "room_id": "RM_ptzWdPTyDKQV", "timestamp": "2026-04-11T09:15:18.042031+00:00"}

Summary

  1. How can I fix the warning below in the Android app?
    ”Received byte stream for topic “lk.agent.session”, but no handler was found. Ignoring.”
  2. Do you have an idea why the “Missing configuration” error is happening in the CLI-deployed agent? I have .env with credentials LIVEKIT_URL, LIVEKIT_API_KEY, and LIVEKIT_API_SECRET defined.