Skip to content

Future: trim HTTP API / super-ollama-only workflows #6

Description

@dkritarth

Context

Plan originally called for only /api/generate and /api/chat on the server; the stock ollama CLI still needs pull/tags/delete routes.

Options

  • Document dual-binary model (current), or
  • Add in-process pull/list so super-ollama can stand alone without full Gin surface

References

  • super-ollama-agent-plan.md — Step 2 (routes) vs model-management note

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions