Skip to content

feat: proj cost track#162

Open
wjiayis wants to merge 95 commits intomainfrom
feat/proj-cost-track
Open

feat: proj cost track#162
wjiayis wants to merge 95 commits intomainfrom
feat/proj-cost-track

Conversation

@wjiayis
Copy link
Copy Markdown
Member

@wjiayis wjiayis commented Apr 24, 2026

No description provided.

Junyi-99 and others added 30 commits January 27, 2026 02:58
#33 

In short, it'll

1. [Frontend] Recognize that user is trying to add a citation (trigger
text is `\cite{`)
2. [Frontend] Temporarily suppress default Overleaf dropdown suggestions
3. [Frontend] Get the last sentence as context for LLM
4. [Backend] Fetch bibliography in `.bib` files as raw text, and remove
irrelevant fields to save tokens
5. [Backend] Call XtraMCP to get paper abstract, using paper title as
key
6. [Backend] Query a fast LLM (hardcoded to `gpt-5.2` for now) to get at
most 3 citation keys
7. [Frontend] Suppress default Overleaf tab-completion to allow users to
accept citation suggestions
Junyi-99 and others added 24 commits March 28, 2026 15:00
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>##
Co-authored-by: andre <95348273+4ndrelim@users.noreply.github.com>
Co-authored-by: Junyi Hou <junyi@xtras3.tail08d22c.ts.net>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Junyi Hou <junyi@xtras3.tail08d22c.ts.net>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
fix as #143/#144 (development) and #140 (main).
Co-authored-by: Junyi Hou <junyi@xtras3.tail08d22c.ts.net>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
### Key changes:
- Select models by ID instead of slug so users can have multiple API
keys for the same slug
- Add loading spinner for save/edit actions
@wjiayis wjiayis requested review from 4ndrelim and Junyi-99 April 24, 2026 12:54
@wjiayis wjiayis changed the title Feat/proj cost track feat: proj cost track Apr 24, 2026
Copy link
Copy Markdown
Member

@4ndrelim 4ndrelim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wjiayis I think there might be some drift between your branch and main. Some of the changes in this PR e.g. in .github/workflows are already committed. Merging this branch now might make the commit history slightly messy. Also, I noticed some of Kah Seng's BYOK changes are also here. It is slightly difficult to isolate the changes introduced for cost tracking.

Could you raise a PR that only reflects your changes for cost tracking?

@4ndrelim
Copy link
Copy Markdown
Member

4ndrelim commented Apr 24, 2026

I see the issue. Your branch is behind main because it was branched off staging, which is the intended workflow.

The problem is that staging and main had already diverged before your changes. Some changes were introduced into both branches separately, so although they are logically the same or very similar, Git treats them as different commits. This is why files such as .github/workflows/... are showing up in the diff even though they are not really part of your intended changes. This should not have been the case, but likely one of us forgot to ensure main and staging remain aligned after introducing changes separately.

Those workflow file diffs should be fine, but your branch should still not include or reflect the BYOK changes. I will fix staging over the weekend to realign it with main and make sure it can continue serving as our staging release branch. I will ensure this moving forward, but for now, i have to trouble you to ideally isolate your changes so it is easier to review and isolate.

@wjiayis
Copy link
Copy Markdown
Member Author

wjiayis commented Apr 25, 2026

@4ndrelim @kah-seng I think main doesn't have IsCustomModel yet, which this PR relies on (to determine whether to track costs or not). What should I use in alternative?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants