Skip to content

Instantly share code, notes, and snippets.

@TobiasGoerke
Last active July 11, 2025 09:05
Show Gist options
  • Select an option

  • Save TobiasGoerke/875cd89906dfa569c0695f8e43e6c0cb to your computer and use it in GitHub Desktop.

Select an option

Save TobiasGoerke/875cd89906dfa569c0695f8e43e6c0cb to your computer and use it in GitHub Desktop.
name: Local Assistant
version: 1.0.0
schema: v1
models:
- name: GPT-4o
provider: azure
model: gpt-4o
apiKey: your-master-key
apiBase: http://litellm:4000
roles:
- chat
- autocomplete
chatOptions:
baseSystemMessage: >-
<important_rules>
You are in chat mode.
If the user asks to make changes to files offer that they can use the Apply Button on the code block, or switch to Agent Mode to make the suggested updates automatically.
If needed consisely explain to the user they can switch to agent mode using the Mode Selector dropdown and provide no other details.
Always include the language and file name in the info string when you write code blocks.
If you are editing "src/main.py" for example, your code block should start with '```python src/main.py'
When addressing code modification requests, present a concise code snippet that
emphasizes only the necessary changes and uses abbreviated placeholders for
unmodified sections. For example:
```language /path/to/file
// ... existing code ...
{{ modified code here }}
// ... existing code ...
{{ another modification }}
// ... rest of code ...
```
In existing files, you should always restate the function or class that the snippet belongs to:
```language /path/to/file
// ... existing code ...
function exampleFunction() {
// ... existing code ...
{{ modified code here }}
// ... rest of function ...
}
// ... rest of code ...
```
Since users have access to their complete file, they prefer reading only the
relevant modifications. It's perfectly acceptable to omit unmodified portions
at the beginning, middle, or end of files using these "lazy" comments. Only
provide the complete file when explicitly requested. Include a concise explanation
of changes unless the user specifically asks for code only.
</important_rules>
You are an expert software developer. You give helpful and concise
responses.
context:
- provider: code
- provider: docs
- provider: diff
- provider: terminal
- provider: problems
- provider: folder
- provider: codebase
services:
vscode:
image: codercom/code-server:latest
volumes:
- vscode_data:/home/coder/.config
- ./workspace:/home/coder/workspace
- ./continue-dev-config.yaml:/root/.continue/config.yaml
ports:
- 8443:8443
environment:
- DEFAULT_WORKSPACE=/home/coder/workspace
user: "0:0"
entrypoint:
- /bin/bash
- -c
- |
code-server \
--extensions-dir /home/coder/.config/extensions \
--install-extension continue.continue && \
code-server \
--extensions-dir /home/coder/.config/extensions \
--bind-addr 0.0.0.0:8443 \
--auth none \
/home/coder/workspace
postgres:
image: postgres:latest
container_name: postgres
environment:
- POSTGRES_USER=pguser
- POSTGRES_PASSWORD=pgpw
- POSTGRES_DB=mydb
volumes:
- postgres_data:/var/lib/postgresql/data
litellm:
image: ghcr.io/berriai/litellm:main-latest
container_name: litellm
ports:
- 4000:4000
environment:
- LITELLM_MASTER_KEY=your-master-key
- DATABASE_URL=postgresql://pguser:pgpw@postgres:5432/mydb
env_file:
- ./secrets.env
volumes:
- ./litellm-config.yaml:/app/config.yaml
command: --config /app/config.yaml
depends_on:
- postgres
volumes:
vscode_data:
postgres_data:
model_list:
- model_name: gpt-4o
litellm_params:
model: azure/gpt-4o
api_base: os.environ/AZURE_API_BASE
api_key: os.environ/AZURE_API_KEY
api_version: os.environ/AZURE_API_VERSION
AZURE_OPENAI_API_KEY=<API Key hier eintragen>
AZURE_API_BASE=<API Base hier eintragen>
AZURE_API_VERSION=<API Version hier eintragen>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment