Skip to content

Sesame-link burns my codex usage immediately #3

Closed
Closed
Sesame-link burns my codex usage immediately#3
Assignees
darkmirage
Labels
area:codexCodex sessionsbugSomething doesn't work as it shouldneeds-infoWaiting on the reporterneeds-triageNot yet looked at by a maintainer

Description

@Makejorton
Makejorton
opened on Oct 11, 2026

What happened

The Codex connection with sesame seems to be creating a feedback loop on my account which burns my 5h session usage limit before I can even get anything done.
I'm not sure I can deliver any evidence of this so I'm hoping I'm not the only on reporting a similar issue.
It's unfortunate because this translates directly into money burnt at the user's expense. Is there a way to resolve this so I can include codex in the sesame-link workflow?

Claude code does not share the same issue.
Thanks for your time.

Steps to reproduce

No response

Sesame Link version

0.1.31 (release)

Computer running Link

macOS, Apple Silicon

Operating system version

Mac OS 15.7.7

Coding tool

Codex

Coding tool version

codex-cli 0.152.0-statusline.3

Where you saw it

Web app on a computer

Output of sesame-link status

Activity

  1. Makejorton
    assigned
    darkmirage
    on Oct 11, 2026
  2. Makejorton
    added
    bugSomething doesn't work as it should
    needs-triageNot yet looked at by a maintainer
    on Oct 11, 2026
  3. github-actions
    added
    area:codexCodex sessions
    needs-infoWaiting on the reporter
    on Oct 11, 2026

  4. github-actions commented on Oct 11, 2026

    @github-actions
    github-actionsBot
    on Oct 11, 2026 – with GitHub Actions

    Thanks for the report. To look into this, please add steps to reproduce:

    • How you start the Codex session (from the web app, sesame-link codex, or another way), and whether you send it any messages.
    • What you see while usage drops: for example, turns starting on their own, repeated messages in the session, or usage dropping with the session idle.
    • Roughly how long it takes to use up the 5-hour limit, and whether it happens with every Codex session or only some.

  5. darkmirage commented on Oct 11, 2026

    @darkmirage
    darkmirage
    on Oct 11, 2026
    Contributor

    @Makejorton just to clarify: is this a result of using the web client or speaking to it over a voice call?

  6. Makejorton commented on Oct 12, 2026

    @Makejorton
    Makejorton
    on Oct 12, 2026
    Author

    @darkmirage Most instances have been voice call within the web app.

  7. darkmirage commented on Oct 18, 2026

    @darkmirage
    darkmirage
    on Oct 18, 2026
    Contributor

    @darkmirage Most instances have been voice call within the web app.

    An issue was found and fixed related to Sesame agents scheduling recurring background tasks that interacted with the coding session poorly. This seems to be what happened in your sessions. I will keep this issue open for now and close it later if no further reports come up.

  8. darkmirage commented on Oct 26, 2026

    @darkmirage
    darkmirage
    on Oct 26, 2026
    Contributor

    Closing this issue. We haven't seen this happen again since the changes were put in place.

  9. darkmirage
    closed this as completedon Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:codexCodex sessionsbugSomething doesn't work as it shouldneeds-infoWaiting on the reporterneeds-triageNot yet looked at by a maintainer

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions