databrickslabs / databrickslabs/coding-agents-databricks-apps
fix: support OpenCode startup with Databricks app SP OAuth
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40
- Forks
- 11
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Problem
OpenCode proxy setup assumes DATABRICKS_TOKEN is present and the terminal prompts for a PAT even when CoDA has a working Databricks app service-principal OAuth profile. This prevents the required Omnigent-attached CoDA path from running without manual PAT injection.
Acceptance criteria
- Allow the content-filter proxy to obtain credentials through app SP OAuth.
- Select the omnigents-host profile for attached terminal sessions.
- Skip the PAT prompt when SP OAuth is valid.
- Retain PAT behavior as fallback.
- Verify Pi and OpenCode launch through Omnigent without manual PAT injection.
Contributor guide
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
Start by tracing the OpenCode and Pi startup paths into the content-filter proxy, then inspect how the omnigents-host profile and DATABRICKS_TOKEN/PAT prompt are selected. Done means attached sessions obtain valid app SP OAuth credentials, skip the PAT prompt when possible, retain PAT fallback, and launch Pi and OpenCode through Omnigent without manual injection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100