Configure TypeScript and Python language servers in Serena container

[Copilot]

Serena container's .serena/project.yml only configured Go, causing TypeScript and Python language server analysis to return empty results.

Changes

• Initialization script: Added /usr/local/bin/serena-init.sh that auto-generates .serena/project.yml with all three languages on container startup
• ENTRYPOINT: Changed from direct serena-mcp-server execution to wrapper script
• Idempotent logic: Script checks for each language individually with anchored patterns (^- go$, ^- typescript$, ^- python$) and only recreates config when any language is missing

#!/bin/bash
set -e
mkdir -p /workspace/.serena

if [ ! -f /workspace/.serena/project.yml ] || \
   ! grep -q "^- go$" /workspace/.serena/project.yml || \
   ! grep -q "^- typescript$" /workspace/.serena/project.yml || \
   ! grep -q "^- python$" /workspace/.serena/project.yml; then
  printf "languages:\n- go\n- typescript\n- python\n" > /workspace/.serena/project.yml
fi

exec serena-mcp-server "$@"

Language servers (gopls, typescript-language-server, pyright) were already installed but not configured for project-level analysis.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[language-support] TypeScript and Python language servers not configured in Serena project</issue_title>
<issue_description>## Summary

The language-support-tester workflow declares support for Go, TypeScript, and Python in the workflow configuration, but the Serena MCP server project is only configured with Go language support. This prevents TypeScript and Python code analysis from working.

Test Results

✅ Go Language Support: WORKING

• Successfully found symbols using find_symbol
• Successfully analyzed Go files using get_symbols_overview
• Successfully found references using find_referencing_symbols
• Tested with: main.go, version.go, main_test.go

❌ TypeScript/JavaScript Language Support: NOT WORKING

• Created test TypeScript file with classes, interfaces, and functions
• find_symbol returned empty results []
• get_symbols_overview returned empty object {}
• Language server not analyzing TypeScript/JavaScript files

❌ Python Language Support: NOT WORKING

• Created test Python file with classes and functions
• find_symbol returned empty results []
• get_symbols_overview returned empty object {}
• Language server not analyzing Python files

Root Cause

The .serena/project.yml configuration file only includes Go:

languages:
- go

However, the workflow configuration at .github/workflows/language-support-tester.md declares:

tools:
  serena: ["go", "typescript", "python"]

Expected Behavior

The Serena project configuration should include all three languages:

languages:
- go
- typescript
- python

Additional Issues

The test sample directories referenced in the task specification do not exist:

• Missing: /workspace/test/serena-mcp-tests/samples/js_project/
• Missing: /workspace/test/serena-mcp-tests/samples/python_project/

These directories should be created with representative test files for proper integration testing.

Steps to Reproduce

1. Run the language-support-tester workflow
2. Attempt to analyze TypeScript or Python files using Serena tools
3. Observe that symbol finding and analysis return empty results

Recommended Actions

1. Update .serena/project.yml to include TypeScript and Python in the languages list
2. Create test sample directories with representative TypeScript and Python code
3. Re-run the language support tests to verify all three languages work correctly

AI generated by Language Support Tester

• expires on Feb 14, 2026, 10:47 AM UTC

<agent_instructions>Fix the serena Dockerfile</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Custom agent used: agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing

• Fixes [language-support] TypeScript and Python language servers not configured in Serena project #801

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR updates the serena-mcp-server container startup behavior to ensure Serena’s workspace configuration enables Go, TypeScript, and Python language-server analysis (previously only Go was configured), aligning container behavior with the repo’s language-support workflows.

Changes:

• Adds a container startup wrapper (/usr/local/bin/serena-init.sh) that ensures .serena/project.yml includes go, typescript, and python.
• Switches the container ENTRYPOINT from serena-mcp-server to the initialization wrapper script.
• Documents the change in BUILD_NOTES.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
containers/serena-mcp-server/Dockerfile	Adds an init script that (re)creates .serena/project.yml and updates the entrypoint to run it before starting the server.
containers/serena-mcp-server/BUILD_NOTES.md	Notes the multi-language initialization behavior and its intended impact.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

When any required language is missing, the script overwrites project.yml entirely. This discards any existing configuration the user may have in that file. Consider updating only the languages: list (preserving other keys) or appending missing languages without clobbering the whole file.

Suggested change

	# Check if project.yml needs to be created or updated\n\
	# Create/update if: file does not exist, OR it is missing any of the three required languages\n\
	if [ ! -f /workspace/.serena/project.yml ] || \\\n\
	! grep -q "^- go$" /workspace/.serena/project.yml || \\\n\
	! grep -q "^- typescript$" /workspace/.serena/project.yml || \\\n\
	! grep -q "^- python$" /workspace/.serena/project.yml; then\n\
	echo "Initializing Serena project with Go, TypeScript, and Python support..."\n\
	printf "languages:\\n- go\\n- typescript\\n- python\\n" > /workspace/.serena/project.yml\n\
	PROJECT_FILE="/workspace/.serena/project.yml"\n\
	\n\
	# If project.yml does not exist, create it with the required languages\n\
	if [ ! -f "$PROJECT_FILE" ]; then\n\
	echo "Creating new Serena project with Go, TypeScript, and Python support..."\n\
	printf "languages:\\n- go\\n- typescript\\n- python\\n" > "$PROJECT_FILE"\n\
	else\n\
	echo "Ensuring Serena project has Go, TypeScript, and Python language support..."\n\
	NEED_UPDATE=false\n\
	\n\
	grep -q "^- go$" "$PROJECT_FILE" || NEED_UPDATE=true\n\
	grep -q "^- typescript$" "$PROJECT_FILE" || NEED_UPDATE=true\n\
	grep -q "^- python$" "$PROJECT_FILE" || NEED_UPDATE=true\n\
	\n\
	if [ "$NEED_UPDATE" = true ]; then\n\
	echo "Appending missing language entries to existing Serena project.yml..."\n\
	{\n\
	echo ""\n\
	echo "# The following languages were added automatically by Serena init:"\n\
	echo "languages:"\n\
	grep -q "^- go$" "$PROJECT_FILE" || echo "- go"\n\
	grep -q "^- typescript$" "$PROJECT_FILE" || echo "- typescript"\n\
	grep -q "^- python$" "$PROJECT_FILE" || echo "- python"\n\
	} >> "$PROJECT_FILE"\n\
	fi\n\

[Copilot]

This note says the container “successfully creates .serena/project.yml when mounting any workspace to /workspace”, but the documented configuration mounts /workspace read-only (:ro), in which case the init script cannot write the file. Update the notes to clarify the workspace (or at least /workspace/.serena) must be writable, or that the script skips initialization on read-only mounts.

Suggested change

	- **Testing**: Container successfully creates `.serena/project.yml` when mounting any workspace to `/workspace`
	- **Testing**: Container successfully creates `.serena/project.yml` when mounting a **writable** workspace to `/workspace`; when `/workspace` is mounted read-only (e.g., with `:ro`), the init script cannot write `.serena/project.yml` and initialization is skipped

[Copilot]

The entrypoint script creates /workspace/.serena and may write /workspace/.serena/project.yml. In the documented usage for this image, /workspace is commonly mounted read-only (:ro), which will cause the container to exit due to set -e when it cannot create/write these paths. Consider detecting a non-writable workspace (and warning + skipping init), or adjusting the image/docs to mount a writable volume specifically at /workspace/.serena (or make /workspace writable).

[Copilot]

The init script hardcodes /workspace paths instead of using SERENA_WORKSPACE (which is set just above and can be overridden by users). Using the env var (with a default) would keep behavior consistent if the workspace location changes.

Suggested change

	# Ensure .serena directory exists in workspace\n\
	mkdir -p /workspace/.serena\n\
	\n\
	# Check if project.yml needs to be created or updated\n\
	# Create/update if: file does not exist, OR it is missing any of the three required languages\n\
	if [ ! -f /workspace/.serena/project.yml ] || \\\n\
	! grep -q "^- go$" /workspace/.serena/project.yml || \\\n\
	! grep -q "^- typescript$" /workspace/.serena/project.yml || \\\n\
	! grep -q "^- python$" /workspace/.serena/project.yml; then\n\
	echo "Initializing Serena project with Go, TypeScript, and Python support..."\n\
	printf "languages:\\n- go\\n- typescript\\n- python\\n" > /workspace/.serena/project.yml\n\
	# Determine workspace directory (allow override via SERENA_WORKSPACE)\n\
	WORKSPACE="${SERENA_WORKSPACE:-/workspace}"\n\
	\n\
	# Ensure .serena directory exists in workspace\n\
	mkdir -p "$WORKSPACE/.serena"\n\
	\n\
	# Check if project.yml needs to be created or updated\n\
	# Create/update if: file does not exist, OR it is missing any of the three required languages\n\
	if [ ! -f "$WORKSPACE/.serena/project.yml" ] || \\\n\
	! grep -q "^- go$" "$WORKSPACE/.serena/project.yml" || \\\n\
	! grep -q "^- typescript$" "$WORKSPACE/.serena/project.yml" || \\\n\
	! grep -q "^- python$" "$WORKSPACE/.serena/project.yml"; then\n\
	echo "Initializing Serena project with Go, TypeScript, and Python support..."\n\
	printf "languages:\\n- go\\n- typescript\\n- python\\n" > "$WORKSPACE/.serena/project.yml"\n\