anomalyco / anomalyco/models.dev
Jev needs a new input modality?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
Jev is currently listed with a text based input and output which makes it look like a chat model.
It's not a chat model and the input isn't actually text.
Shouldn't Jev be given a new json input type? Jev actually takes schema like:
{
"state": {
"ticket_message": "My flight was cancelled. Can I get a refund?",
"refund_policy": "Cancelled flights are eligible for a full refund."
},
"questions": {
"policy_supports_refund": {
"type": "noul",
"instructions": "Does the refund policy support the refund requested in the ticket?"
}
}
}
https://docs.typesafe.ai/concepts/how-to-build-with-system-one#example-send-only-relevant-context
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
Open models/typesafe/jev-latest.toml around line 22 and compare Jev's current input and output metadata with the linked Typesafe example. Update the metadata so Jev is represented with its JSON/schema input rather than text input, then verify the model entry no longer presents it as a chat model.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100