Also thinking deeper, I think your question also is very broad on aspects to answer.
Technically in times where there is a gathering of ai and people I think a single chat surface is not the right experience but yeah having a UI saying agents as tabs felt tooo boring and actually fed up.
Just wanted to keep it fun but at the same time can we elevate the experience when there is a common surface where a bunch of ai-npcs and people can meet.
I hope it answers, happy to dig more in a different direction if you felt I understood it wrong
I definitely love the format, but the real reason is each town comes with it's own creative story, theme and interaction rhythm. I first thought about making one town that held them all which I wanted to have for myself or say my own town. But then later thought different people want to have their own representation of it, since it's english, different themes and all about creativity it has no bounds.
In the hindsight I also wanted to figure out which experiences it improves vs which it decorates. Curious what you felt when you experienced it.
hey thanks for the feedback, agreed there are a lot to get right
1. If you have self hosted it yes then we need OpenAI api key, we are also working to get things working with llama so should be available soon (but if from cloud you shouldn't have got this error)
2. We also have moved away from openAI embedding (BGE-M3) to our own hosted in the cloud.
In self host we already have claude code support happy to help there
We faced the same challenge while building SOL (https://github.com/RedPlanetHQ/sol) — a personal assistant that relies heavily on memory for context and continuity.
Getting LLMs to invoke memory tools at the right time is definitely trickier than just wiring up MCP correctly. We're still refining it, but we've made good progress by explicitly guiding the assistant within the system prompt on when and how to use memory.
Using something on similar lines as rules in claude/cursor etc has been working better. It’s not perfect yet, but this combination of prompt engineering and structured tool exposure has been moving us in the right direction.
We are working on it, LLaMA models are not working good when it comes to finding facts from the message. We should have this out in the next couple of days
Hey, we are still early and are figuring out things. Thanks for being candid, was there something you are interested in seeing in the product? (use case, feature etc)
Current AI functionalities: 1. AI-generated Titles 2. Smart Delegation 3. Duplicate Detection 4. AI Summarization 5. AI filtering 6. Automated Triaging
We are almost done working in 2 other areas
1. AI assistant while create a new issue ensuring the issue has enough information
2. Chat assistant to interact with the tool
Really appreciate the thoughts. The places where we believe AI matters a lot is
1. Ensuring ticket has enough information
2. Offloading some amount task before someone picks it.
These are the 2 key areas we are focusing and we will launch some features around these in the coming weeks. Would love to hear if there are some other places you feel we can focus on?
Thanks for the feedback. We started this 4 months back and these are a few features we build. In the journey and as customers started using we figured out more strong features.
1. Context enricher - To ensure the ticket has enough information
2. AI agents - To offload some part of the work.
Hey, we have something in personal task management in our roadmap. We are still exploring how to solve that problem. Happy to hear thoughts on how you do it right now. https://github.com/tegonhq/tegon/issues/131
1. We started our documentation at https://docs.tegon.ai, though it is not ready yet points taken, and we will work towards making more documentation.
2. We are planning internally to bring more systems to how we manage PRs and to have the right information on them.
3. We love opensource and we have built all our previous products opensource. Keeping our love aside we believe the building of a marketplace for agents/integrations is where the community can help us a ton. We are currently working on making that more modular so that people can start contributing.
What we have done till now started with the basic Project management and there is a lot more to be built and to solve.
Hey, that's where we bring in triage grouping and duplicate identification. We show you what are the similar issues and we are also working on smart merging so to merge the information from both the issues.
Just wanted to keep it fun but at the same time can we elevate the experience when there is a common surface where a bunch of ai-npcs and people can meet.
I hope it answers, happy to dig more in a different direction if you felt I understood it wrong