Skip to content

feature request, restful api / exposure #162

Closed as not planned
Closed as not planned
@aratic

Description

@aratic

hi team,

was playing interactive mode for couple hours, pretty impressive

resides what's mentioned in #145 ,
it might be not too far, to plug this a endpoint / functional call ( like swig or socket or openapi to replace current stdin ?, then self-host can have a very powerful new residents, like i got a powerful PC at home to be personal assist

also found that -n is the context / token limit, would be great if engine can start with 0 presume context ( which is to lift off / decouple a bit from stdin

kindly let me know if there are directions or others interested in this ( also a developer here but not so C / tensor flavored
( as without advice, force hi-jack stdin / stdout seems stupid

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already existsenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions