github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 13:19:40 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #7738] Allow passing file context for FIM tasks on /api/generate #4941

New Issue
Closed
opened 2026-04-12 16:00:10 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 16:00:10 -05:00
Owner
Copy Link

Originally created by @boswelja on GitHub (Nov 19, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7738

It's relatively common now that FIM tasks use additional "context" - files related to the FIM task - to better perform their task.
Generally this context includes the file path + name, as well as the contents.

Enter the problem, models use different tokens to denote the start/end of this information. For example, deepseek-coder looks like

# /path/to/file.java
package com.my.app

class MyApp {
}

And StarCoder has different tokens (and some extra data)

<reponame>MyGitRepository
<filename>/path/to/file.java
package com.my.app

class MyApp {
}
<|endoftext|>

It'd be neat if we had a model-agnostic way of handling this, similar to how suffix works now

Originally created by @boswelja on GitHub (Nov 19, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7738 It's relatively common now that FIM tasks use additional "context" - files related to the FIM task - to better perform their task. Generally this context includes the file path + name, as well as the contents. Enter the problem, models use different tokens to denote the start/end of this information. For example, deepseek-coder looks like ``` # /path/to/file.java package com.my.app class MyApp { } ``` And StarCoder has different tokens (and some extra data) ``` <reponame>MyGitRepository <filename>/path/to/file.java package com.my.app class MyApp { } <|endoftext|> ``` It'd be neat if we had a model-agnostic way of handling this, similar to how `suffix` works now
GiteaMirror added the feature request label 2026-04-12 16:00:10 -05:00
GiteaMirror commented 2026-04-12 16:00:12 -05:00
Author
Owner
Copy Link

@boswelja commented on GitHub (Jul 27, 2025):

I believe this has been implemented already

<!-- gh-comment-id:3123818268 --> @boswelja commented on GitHub (Jul 27, 2025): I believe this has been implemented already
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#4941
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?