Skip to content

Add inkeep extension#17495

Merged
thomaspaulmann merged 10 commits intoraycast:mainfrom
marcklingen:ext/inkeep
Mar 3, 2025
Merged

Add inkeep extension#17495
thomaspaulmann merged 10 commits intoraycast:mainfrom
marcklingen:ext/inkeep

Conversation

@marcklingen
Copy link
Contributor

@marcklingen marcklingen commented Mar 2, 2025

Description

Adding a new extension for the Inkeep completions API will assist teams using Inkeep for customer-facing documents. This extension enables them to answer questions about their products more easily.

Screencast

inkeep-raycast-extension.mp4

Checklist

- chore: improve readme
- feat: implement initial version (raycast#1)
- init
@raycastbot raycastbot added the new extension Label for PRs with new extensions label Mar 2, 2025
@raycastbot
Copy link
Collaborator

Congratulations on your new Raycast extension! 🚀

Due to our current reduced availability, the initial review may take up to 10-15 business days

Once the PR is approved and merged, the extension will be available on our Store.

@nick-inkeep
Copy link

Founder at Inkeep here - endorsing/looks good to me.

@pernielsentikaer pernielsentikaer self-assigned this Mar 3, 2025
@pernielsentikaer
Copy link
Collaborator

Looks really nice @marcklingen 🔥

I'll get @greptileai to have a quick look 😊

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Added a new Inkeep extension for Raycast that enables users to interact with the Inkeep Completions API to get AI-powered answers from their knowledge base.

  • The CHANGELOG.md entry should use {PR_MERGE_DATE} instead of the hardcoded date "2025-03-02" to follow repository conventions
  • The command name in package.json is "ask-inkeep" but the title is "Inkeep" - consider using a more descriptive title like "Ask Inkeep" to match the functionality
  • The handlePromptSubmission function in ask-inkeep.tsx should be wrapped in a try-catch block as it's a launch command
  • Consider using showFailureToast from @raycast/utils instead of manually creating error toasts in the error handling sections

10 file(s) reviewed, 6 comment(s)
Edit PR Review Bot Settings | Greptile

Copy link
Collaborator

@pernielsentikaer pernielsentikaer left a comment

Choose a reason for hiding this comment

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

Bot an I added a few suggestions, could you look into them :)

Request a new review when you are ready. Feel free to contact me here or at Slack if you have any questions.

@marcklingen
Copy link
Contributor Author

Bot an I added a few suggestions, could you look into them :)

Request a new review when you are ready. Feel free to contact me here or at Slack if you have any questions.

This all looks like valid review feedback, will push an update in a bit

@pernielsentikaer
Copy link
Collaborator

Awesome, let me know if anything pops up :)

I would also move uniqueLinks to around line 18 to avoid recalculation on every render 😊

- fix: improve streamed markdown rendering
- chore: implement review feedback
@marcklingen
Copy link
Contributor Author

Awesome, let me know if anything pops up :)

I would also move uniqueLinks to around line 18 to avoid recalculation on every render 😊

will do

@marcklingen
Copy link
Contributor Author

@pernielsentikaer aside from naming discussion above, this should be good to go now, thanks again for the speedy review!

@marcklingen
Copy link
Contributor Author

Naming update pushed as well, fyi @pernielsentikaer

@pernielsentikaer
Copy link
Collaborator

You're missing evals for tool calls, you can check here on how to add it: https://developers.raycast.com/ai/write-evals-for-your-ai-extension - could you look into this? 😊

@marcklingen
Copy link
Contributor Author

You're missing evals for tool calls, you can check here on how to add it: https://developers.raycast.com/ai/write-evals-for-your-ai-extension - could you look into this? 😊

Sure, based on the docs I assumed this is optional

@pernielsentikaer
Copy link
Collaborator

Thanks for flagging and taking a look at this; we'll improve this guide 😊

@marcklingen
Copy link
Contributor Author

Thanks @thomaspaulmann!

@thomaspaulmann thomaspaulmann merged commit e23ed2a into raycast:main Mar 3, 2025
9 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2025

Published to the Raycast Store:
https://raycast.com/marcklingen/inkeep

@raycastbot
Copy link
Collaborator

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@marcklingen).
Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.

@marcklingen
Copy link
Contributor Author

Thanks everyone for the speedy review, did not expect this to launch today 🙏

@marcklingen
Copy link
Contributor Author

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@marcklingen). Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.

done -> raycast beta access would be really nice :)

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

Labels

AI Extension new extension Label for PRs with new extensions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants