Raycast extension for try
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4k
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I really like try. I often live inside Raycast, so I built a Raycast extension that reproduces the core behavior of try (fuzzy search of experiment directories, date‑prefixed names, time‑aware sorting, etc.), so I can use the same workflow directly from the launcher.
The logic is essentially a reimplementation of your tool for the Raycast environment. I’ve kept the MIT license and credited tobi/try in the README and in the extension description.
Right now the code is on GitHub:
I’ve also opened a PR to add this extension to the Raycast extensions (so it can be installed from Raycast). If you’d prefer that this not be published, or if you have any concerns about how I’ve reused the idea/logic, I’m very happy to change things or close the PR.
Thanks again for building try – it really fits how my brain works, and it inspired this extension.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point in the try repository is named. Start by reviewing the linked extension repository and the Raycast extensions PR; done would require a maintainer decision about whether and how this external integration should be adopted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100