Conversation
…ding The new-conversation screen replaces its three starter cards with a two-way toggle — I want to fund (blue, arrow out) / I need funding (emerald, arrow in) — remembered per browser and defaulting to the researcher's side. The choice goes to the backend with the conversation as its intent, so the assistant drafts an RFP or a proposal without guessing; the regex that inferred the work type from the opening message is gone, along with the defaultArticleType seam it fed. Under the composer a researcher gets two calls to action: connect their researcher profile (ProfileEditModal narrowed to ORCID and Google Scholar) and apply to a specific RFP (the existing selector; the choice is sent with the conversation and lands on the proposal it creates). A funder gets one line to talk to the ResearchHub team. Shared pieces: components/Funding/fundingDirection.ts and FundingDirectionIcon carry the arrow-and-colour language, which the My Funding tabs now use too; ButtonGroup options take an activeClassName; ProfileInformationForm can show a subset of its social links. Verified with type-check, eslint and prettier only. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 22, 2026
|
This was referenced Sep 22, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



The new-conversation screen replaces its three starter cards with a
two-way toggle — I want to fund (blue, arrow out) / I need funding
(emerald, arrow in) — remembered per browser and defaulting to the
researcher's side. The choice goes to the backend with the conversation
as its intent, so the assistant drafts an RFP or a proposal without
guessing; the regex that inferred the work type from the opening message
is gone, along with the defaultArticleType seam it fed.
Under the composer a researcher gets two calls to action: connect their
researcher profile (ProfileEditModal narrowed to ORCID and Google
Scholar) and apply to a specific RFP (the existing selector; the choice
is sent with the conversation and lands on the proposal it creates). A
funder gets one line to talk to the ResearchHub team.
Shared pieces: components/Funding/fundingDirection.ts and
FundingDirectionIcon carry the arrow-and-colour language, which the
My Funding tabs now use too; ButtonGroup options take an
activeClassName; ProfileInformationForm can show a subset of its social
links.
Verified with type-check, eslint and prettier only.
Stack
Part of turning the AI Mode overlay into a funding workspace (plan and mock decisions in the first PR's thread). Stacked on #1117; merge that first, then this one.
🤖 Generated with Claude Code