University of Tuebingen course projects for building modern, agentic study systems.
StudyOS is the shared GitHub home for the practical course Build your own StudyOS with Modern Agentic Systems. The organization collects student-built tools, experiments, SDKs, and collaboration infrastructure around university study workflows.
| Metric | Current Snapshot |
|---|---|
| Public repositories | 4 |
| Human contributors | 10 |
| Main branches protected | 2 of 5 |
| Course context | ML-4510 Practical Machine Learning, summer term 2026 |
| Data refreshed | 2026-06-21 |
| Repository | Focus |
|---|---|
| StudyPlanner | Web and agent-enabled study planning app with course catalog, weekly planner, transcript import, PO progress tracking, and OpenAPI/MCP catalog search. |
| StudyOS_Agent | Android and Flutter-based StudyOS agent work for University of Tuebingen study workflows. |
| study-os-thesis | Thesis and lecture matching tool for StudyOS seminar workflows. |
| tue-api-wrapper | SDKs, native clients, and apps for University of Tuebingen study systems such as Alma, ILIAS, Moodle, TIMMS, campus data, and student workflows. |
The organization also maintains .github for the profile and shared GitHub metadata. It is intentionally not counted as a project repository.
StudyOS is built by students and collaborators across the organization:
| Contributor | Repositories |
|---|---|
| SebastianBoehler | StudyOS_Agent, tue-api-wrapper |
| Kyotoo-chan | StudyPlanner |
| EmWhyy | StudyPlanner |
| linuscooper | StudyOS_Agent |
| MertOkur | StudyOS_Agent |
| ValentinJSchmidt | study-os-thesis |
| dxmme | study-os-thesis |
| lenabinder1001 | StudyPlanner |
| mxs01 | study-os-thesis |
| ydankner | StudyPlanner |
- Keep university credentials and private study data local by default.
- Prefer small, reviewable pull requests with clear ownership.
- Reuse shared wrappers, clients, schemas, and workflow patterns where possible.
- Let humans approve and merge; automation supports review and implementation.
Open the repository that matches your project area and follow its README. New ideas usually start as GitHub issues with scope, acceptance criteria, risks, and test expectations before becoming implementation pull requests.