You are browsing as a guest. Sign up (or log in) to start making projects!

4h 8m 18s logged

Devlog#11 - Things went the Otherways.

Greting everyone!

TL;DR - for those who dont want to read long story -

Spent most of the day debugging and rethinking the Ollama integration, which exposed problems with building around a thinking model. After testing the full workflow, I decided to move to Qwen2.5-Coder 7B and introduce Stage X to realign the architecture before continuing development.

Long Story - for those who are interested 🙋:

SO i was working towards local LLM integration for my project as mentioned in the previous devlog. Today was a sunday so had a lot of time on me so worked on this.

i decided of making ollama the sole provider for AI for v1 of my project as it is easy to work with. I chose initially qwen3:8b model. i was working with it for the ollama integration and model works perfectly and give answers and checkning for bugs errors and debugging and adding more tests etc.

today most of the time went into debgging,investigating, rediscovering how the existing architecture actually worked, challenging earlier assumptions, and then rethinking the architecture around what the system really needs.

  • The first major objective was making sure the complete Python-project path worked together rather than only working as isolated components. The question was whether these pieces actually behaved correctly as one pipeline. So assessed the code and assemebled it and strenghted it and then added tests for it.

  • Now working with ollama’s qwen3:8b model but soon ralzied it was a major mistake. i wanted to make the model to communicate with the project. So it worked kind off. Like the model i was using was a model that thinks and has chain of thoughts. But soon it became a problem for me.

  • our first integration attempt exposed a problem. The model was clearly behaving as a thinking model. that mattered bcz Context Forge was now trying to use it as a part of a deterministic workflow.

  • The model’s internal thinking could consume substantial generation time before producing the actual answer.That made the original integration architecture less suitable for the project.

  • So i asked myself some questions and came to a conclusion that i should build v1 around the non thinking models like the one i will be using now on is qwen2.5-coder:7b . and integrate thinking and AI providers in future versions.

THE CURRENT MODEL ARCHITECTURE should work with a non thinking model.

So i introduced a phase for now called StageX where i would check the code and try to refactor it acc to the new direction we are heading.

what will StageX chenage:

  • Model Asumptions
  • Thinking or reasoning done by the model
  • Adding a Config file feature- CLI Behaviour(improved)
  • Better Ollama integration
  • Operational Logging

this all we implemented in span of some days as i’ve got exams coming but will work on it.

a large part of time not logged onto hackatime was spent towards rethinking the decisions made in the past and plan out the Future.

TH biggest progress from this was architectural clarity.
LET”S START STAGEX

Thank u for reading this brain DUmp of Mine. Stay Tuned for future updates

0
39

Comments 1

@vxyzln

!!!!