9 ms·

Show HN: Tegon: Open-source alternative to Jira, Linear

163 points by harshithmul 2y ago

Hi HN, we're Harshith, Manoj and Manik and we're building Tegon (https://github.com/tegonhq/tegon https://github.com/tegonhq/tegon), open-source issue tracking software that uses AI to smartly automate manual workflows or provide more context to engineers for a given task. There's a demo video here: https://www.loom.com/share/b664b01e9b064a02be5791c12b77a107 https://www.loom.com/share/b664b01e9b064a02be5791c12b77a107, and you can try out the product at https://demo.tegon.ai https://demo.tegon.ai using these credentials: Email: elon@xyz.com Password: XfFNw6GwVJVQv6PA As engineers, our experience with traditional tools like Jira hasn't been great. It is slow, bloated and often acts as a burden to engineers. These tools didn't help engineers in getting the work done faster, they only helped the management in tracking the work which enabled a lot of processes and micro-management which used to kill our productivity. With the rise of LLMs, we thought about how project management and issue tracking would look 5-10 years from now. The current tools didn't match our vision, which excited us and started the journey of Tegon. We aim to build a tool where manual workflows are either automated or handled by AI. This tool will provide better context about a task to an engineer by smartly gathering data from all sources, helping teams with better prioritization. Tegon loads all the data from local (indexed db) thus making it super fast to load and navigate. We make all of this happen by real-time sync in the background. Tegon also uses AI to simplify the issue-creation process by automatically creating titles, suggesting labels and assignees and identifying duplicates. Tegon also simplifies the issue creation process from Slack, just apply an emoji to a Slack message and a tegon issue will be created making it easier for other teams to raise bugs or feature requests to engineering teams. We deeply value the feedback from this community and have spent the last month revamping Tegon's design based on the feedback from our last launch. We just got started and there's a lot more to come. We're eager to get more feedback and keep building. Let us know what you think in the comments :)

latchkey 2y ago
Finally got around to checking this out and got: "no healthy upstream"
Daviey 2y ago
Thanks for sharing, can you tell us more about the functionality that AI has in your product and what Cohere does for you, above the capability of OpenAI? Ta
- harshithmul 2y ago
  Current AI functionalities: 1. AI-generated Titles 2. Smart Delegation 3. Duplicate Detection 4. AI Summarization 5. AI filtering 6. Automated Triaging Cohere: To improve smart delegation, duplicate detection, and automated triaging, we integrate Cohere's advanced NLP capabilities, ensuring more accurate and efficient similar issue searches. We are bringing in more agents to delegate some of the work to them. 1. Code agent: This will help you in solving the small code fixes and small features but assigning issues to the agent and giving it instructions on how to solve them. 2. PRD agent: To help in PRD writing for the PM we'll add more agents for different use-cases going forward
  - magicalhippo 2y ago
    We have several working at support who struggle with writing good issues due to dyslexia, lack of technical knowledge (domain experts) or similar. Was curious if the AI could assist them in a useful way. Sometimes they might poorly explain the problem, which module it pertains to or similar or similar, making it very unclear what exactly the issue is. I was thinking perhaps an AI component that could analyze what they said and "complain" if the AI detects key information is lacking, or perhaps just re-summarize what they wrote so it becomes more clear when they haven't supplied sufficient information.
    - harshithmul 2y ago
      That sounds exactly like something which we will be launching next week. We are working on an AI assist which will ask questions while creating issues in aspects like 1. If that can be broken into sub-issues 2. If it lacks information according to a template that's created in association with the label. For example: Label bug: You can explain in the template what is expected (Some deployment information, logs, screenshots etc.) and the AI assistant will help in ensuring those contents exist. We are also exploring if there are more such cases where AI can help. Do let us know your feedback on this once we launch
karpovv-boris 2y ago
[flagged]
- darkhorse13 2y ago
  Completely disagree. Their website is fairly unique, and looks really nice and usable. It's a bit "standard" with the gray, but that's fine if that's their branding.
  - dewey 2y ago
    Unique? It looks like a Linear clone...but without the polish and design skills.
  - meiraleal 2y ago
    It looks good indeed. Unique isn't the best way to describe it tho.
- n3storm 2y ago
  Imho, all too rounded buttons make them look like tags which has much less importance than controls.
- hardwaresofton 2y ago
  It's wild to see this posted on hackernews. I'm pretty sure hn has no problem with user traction.
- kshri24 2y ago
  Looks good to me.
wanderingmind 2y ago
If you are planning to monitise it through SaaS, might be worthwhile to change the license to AGPL from MIT.
- harshithmul 2y ago
  Thank you for your suggestion. You’re absolutely right; we are actively exploring licensing options, including AGPL, to ensure that our product remains protected. We value input from the community and are open to suggestions and assistance in making this decision. Our goal is to prevent unauthorized copying and resale of our product under different names while fostering a collaborative and innovative environment.
  - zamalek 2y ago
    While the community may be a good source for ideas, you should retain an attorney. The community is not your lawyer. There's also the BSL. It specifically calls out competitive products. It automatically falls away for code older than a given time to another OSI license: https://en.wikipedia.org/wiki/Business_Source_License https://en.wikipedia.org/wiki/Business_Source_License. Per the Wikipedia article this still has issues: contributors are handing over their work for to you for free for that duration, they can't use their own work for profit. The AGPL does make your project extremely unattractive to competition, without affecting your contributors. The issue is that it is still possible to compete with you using it, so long as your competition releases all their code (i.e. infra, billing, etc.) under AGPL. I would personally go for AGPL because it will keep the worst offenders (Amazon, Microsoft) away from your code.
    - harshithmul 2y ago
      Understood, Thank you. Really appreciate all that information.
    - KolmogorovComp 2y ago
      Using BSL would make their code source-available but it wouldn’t be open-source anymore, unlike AGPL.
circularfoyers 2y ago
Do you support local LLMs? I could only see an ENV for OPENAI_API_KEY.
- Manik_agg 2y ago
  Hey another co-founder of Tegon here, currently we only support Open AI models but plan to add local models support with Olamma soon.
- hrpnk 2y ago
  There is also COHERE_API_KEY for the vector storage & search: https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/src/modules/vector/vector.service.ts#L30 https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61...
- ranger_danger 2y ago
  llama.cpp supports being an OpenAI API server, you would just need to change the URL in the Tegon source.
deepak_sozial 2y ago
how is it different from the mighty plane.so?
- lawgimenez 2y ago
  Why does plane.so look exacly like linear.app?
  - tommoor 2y ago
    I think you can guess
    - lawgimenez 2y ago
      Yeah, I just searched some past discussions regarding plane. Not good
- harshithmul 2y ago
  Plane.so is indeed a great tool, and they emphasize creating an unopinionated platform that can be utilized by anyone. Our approach, however, is AI-first. We are focused on integrating multiple AI agents into our tool to assist stakeholders in various ways, including automating manual tasks, providing enhanced context, and even resolving issues end-to-end. Our goal is to leverage AI to significantly boost productivity and streamline workflows for our users.
deleted 2y ago
[deleted]
throwaway_fjmr 2y ago
I logged in around 2024-07-09 10:22 UTC, and I hope the stories in review don't get accepted. You might want to demo the product in a slightly less open way, though.
- harshithmul 2y ago
  Currently, our cloud service isn't publicly accessible, so we've been exploring the best way to demonstrate our product's features and functionality. To address this, we've created some demo credentials and a product instance for demo purposes. Additionally, we've taken a snapshot of a cleaner version of the product, which we refresh weekly. We will also explore more to see if there is a better way to do this.
faust201 2y ago
Would it be possible to run AI/ML on an existing jira/github large project (k9mail/KDE(gitlab) and show/prove this can be useful/better etc? Thanks
- harshithmul 2y ago
  We haven't yet modularized the AI features of our product. Currently, it's not possible to use the AI features on top of JIRA/GitLab. Our AI capabilities have achieved better accuracy and output because we have more control over the infrastructure and the product's foundations. Additionally, incorporating agents and managing their workflows require a distinct set of metadata and separate workflows, which we are still in the process of exploring.
  - magicalhippo 2y ago
    Since one can self-host Tegon, do you have some importers working? That way I could import some Jira issues and see it in action on our own data. If you have an API to manage issues, that could work as well. Would need that anyway for custom build integration etc.
    - harshithmul 2y ago
      We are in the process of building those scripts. As we are working with companies for migration we started to improve these scripts to cover more edge cases. These should be out sometime soon. Otherwise, we have a public API to do CRUD operations for all important entities (issues, labels etc). We are working to get an openAPI spec once that is out we should have all the APIs added to our https://docs.tegon.ai https://docs.tegon.ai
      - magicalhippo 2y ago
        Sounds great, will keep an eye out.
  - Aeolun 2y ago
    Can you give me an idea of what you are using AI for currently? Edit: Never mind, found the list you posted elsewhere.
itomato 2y ago
What evidence do you have that suggests auto-generated titles are better?
- harshithmul 2y ago
  We thought auto-generated titles could make life a bit easier. Creating the perfect title for every task can be tricky, especially when things get complicated. So, we added this feature to help with that. (This is also something I faced as a challenge while I was working in Airbyte the community does a great job at explaining the issues but we always have to edit the title to make it more crisp.) Right now, we’re using the product ourselves and trying it out with a few customers. We’ve noticed that for simple placeholder tasks, a straightforward title works just fine. But for more detailed tasks with longer descriptions, the auto-generated titles seem to work better. We’re still experimenting and gathering feedback to make it even better. Examples from our board: Description: - utils.py 228 : Failed to call LLM with the following error: BedrockException Invalid Authentication - An error occurred (UnrecognizedClientException) when calling the InvokeModel operation: The security token included in the request is invalid. Title: Feat: Investigate Salesforce cloud version error: Invalid Authentication Description: Triage ux bug - once i decline or accept a triage request, it re-directs me to issues screen. Ideal behaviour to be at the triage list view where you either show removing it from triage or highlighting that an action have been taken on this request. Title: Redirect user to Triage List after Accepting/Declining Request
  - itomato 2y ago
    Lack of "crispness" in user titles is a tooling problem? Isn't this "wrinkly" technical detail lost?
    - harshithmul 2y ago
      We were experimenting if it could potentially help in taking that off the plate. Feedback taken we will work on improving that or taking a call based on how it performs.
  - deleted 2y ago
CapeTheory 2y ago
IMO the absolute most important thing with a tool like this is performance. I have to sign in to a handful of cloud desktops each week and interact with customer Jira/Confluence/AzureDevOps/etc pages, and the big thing which kills my engagement is the app not being snappy enough. Doesn't matter how many of the features our Agile SAFe scrum wizard wants me to use, I'm not going to bother if there is too much friction. These apps inevitably require a lot of clicks, so latency becomes very noticeable.
- harshithmul 2y ago
  True performance is our priority. From the very beginning, we focused on ensuring that our app ran smoothly and quickly. To achieve this, we load all the data locally, allowing you to experience everything at lightning speed. Our background server keeps your data synchronized seamlessly between the server and the client, so you get the best of both worlds: speed and reliability.
  - denysvitali 2y ago
    > True performance is our top priority The server is written in Node.JS
    - harshithmul 2y ago
      My bad. We focused on the performance on the front end currently, as said before we loaded all the data locally and kept the data synced in the background to make the interactions fast. We chose nodejs as that was easy for us to get started with. But definitely, if things get hampered we will start looking into it.
      - giovannibonetti 2y ago
        Good call. Front-end performance is often the bottleneck. Preloading most of the required data in advance is really helpful. Trello does just that and it is one of the snappiest web apps.
    - 2y ago
peterldowns 2y ago
First, congratulations on launching. I think people are so used to seeing beautiful products these days that it can be hard to remember how hard it is to make anything. Nice work! With that out of the way, here is some critical feedback: - What is the pitch that you made to YC that convinced them to back you? The market size just doesn't seem that large and I don't understand what will differentiate you from Linear (whose design language you seem to have ripped off, somewhat poorly.) This post and the current featureset is vague and does not seem like a significant improvement. What is the core problem you're solving and why is that valuable? Your launch post above describes a lot of "how" but not a lot of "why". - Why are you bothering to pretend to be "open source"? You're backed by YC and you'll make money selling access to the product on your "Tegon Cloud". If you're really going to be open-source, you need to make some significant improvements before anyone would consider contributing. Some documentation on how to self-host would be a good start. Look at all the environment variables in this dockerfile — which ones are necessary to run this service myself? https://github.com/tegonhq/tegon/blob/main/docker-compose.yaml#L55 https://github.com/tegonhq/tegon/blob/main/docker-compose.ya... - If you're going to be "open source", the quality of your codebase and engineering skills is going to be a deciding factor in whether or not you get outside contributors. Consider writing actual descriptions in your pull requests, describing what you've done and why. Here's a PR picked at random — this is bad engineering work and does not encourage others to contribute. https://github.com/tegonhq/tegon/pull/114 https://github.com/tegonhq/tegon/pull/114 My advice is that you drop the facade of being "open source", hire a designer, and do some actual user research to figure out where people are actually struggling with their ticketing systems. The features you're building (automatic title suggestion, thread summarization, and "find similar tickets") do not solve the problems that I have had with ticketing systems. They're small, potentially nice-to-have features that absolutely do not help me understand the core question for all engineering teams: who is doing what, how will they do it, why, and when will it be done.
- peter_l_downs 2y ago
  By the way, you've left the notiz.dev LICENSE file in your server code, probably you want to remove that. https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/LICENSE https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61... Separately, there seems to be a ton of unused or broken or dead code sprinkled throughout — for instance, in the auth code, I can't tell if you're doing basic email/password auth or using Supertokens and a third-party login via Google. You have code for both and some routes seem dead or missing. https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/frontend/src/modules/auth/signin-form.tsx https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61... Also, I mentioned the lack of documentation for how to run Tegon locally because your docs are entirely insufficient. The main docs page is just a README template. https://github.com/tegonhq/tegon/tree/main/docs https://github.com/tegonhq/tegon/tree/main/docs The quickstart guide has a broken link to instructions on how to self-host https://github.com/tegonhq/tegon/blob/main/docs/quickstart.mdx#self-hosted https://github.com/tegonhq/tegon/blob/main/docs/quickstart.m... The oss/local-setup guide is entirely empty https://github.com/tegonhq/tegon/blob/main/docs/oss/local-setup.mdx https://github.com/tegonhq/tegon/blob/main/docs/oss/local-se... The oss/deploy-tegon guide does not explain anything and the script it references seems out of date https://github.com/tegonhq/tegon/blob/main/docs/oss/deploy-tegon.mdx https://github.com/tegonhq/tegon/blob/main/docs/oss/deploy-t... I'm done looking at this project. I strongly recommend hiring the best engineer you can find as quickly as you can.
romanshamin 2y ago
[dead]
mort96 2y ago
> AI-first I would've been interested in an actual replacement for Jira/Linear, but I'm uninterested in an unreliable tool where I have to deal with hallucinations. Stop trying to cram this crap into every single software project.
- codegeek 2y ago
  Unfortunately, you need "AI First" to have any chance of VC funding for the past 2 years or so. They are probably keeping this in mind.
  - mort96 2y ago
    That may be, but you need to not have "AI" or "AI-first" in your description in order to be an interesting product/project.
  - giancarlostoro 2y ago
    The most obvious thing that should be done instead is to make an API spec that AIs can consume for your service, a common spec that if you target, any AI assistant can talk to freely. I feel like we're just over complicating things and burning money. Let the AI people burn their time and energy on the AI, let normal people build useful intuitive tools.
maximilianburke 2y ago
I'm getting a "no healthy upstream" error from the demo link.
- harshithmul 2y ago
  We started seeing people creating random issues we will get it back up after cleaning it a bit
hrpnk 2y ago
I was interested in how the duplicate detection of issues is working. It uses Cohere API for embeddings (full issue text) [1] and vector-based similarity search [2]. [1] https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/src/modules/vector/vector.service.ts#L66-L85 https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61... [2] https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/src/modules/vector/vector.service.ts#L125-L136 https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61...
- harshithmul 2y ago
  We tried different approaches, we made a recent change where we started using cohere for re-ranking and embedding which did give really good results. Happy to create an account for you to try it out. harshith [@] tegon.ai
shafyy 2y ago
I don't know how to write this comment so it doesn't come off as unconstructive. But here you go. - "AI-first"? What does that even mean? Calling some API to auto-generate a title? Do you really think that a) this solves a big user problem and b) that Linear can't add that in two seconds if they wanted to? - Open-source and VC-backed? Please stop bull shitting me, and yourself. - What is your USP? That you're faster than Jira? Fine, but this is not 10 years ago and snappy tools like Linear exist (and I'm not even a fan of Linear). - elon@xyz.com? Really? Please use your time and talent for something else than this VC AI pipedream. Or don't, I'm just a rando on HN.
- harshithmul 2y ago
  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. We will be getting these out soon
- mdeeks 2y ago
  > that Linear can't add that in two seconds if they wanted to? FYI Linear has had this feature for a while. It works quite well.
johntash 2y ago
Do you think this would be useful for personal users as a todo/task management app? I have no chance of convincing work away from Jira, but I'm always on the lookout for a better personal task manager.
- harshithmul 2y ago
  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 https://github.com/tegonhq/tegon/issues/131
yamumsahoe 2y ago
linear set the bar so high but different projects have different needs.. i wonder how tegon and linear compare side by side.
haswell 2y ago
Having worked quite deeply with Jira and a host of other enterprise products that target this set of use cases, and having a pretty good understanding of what decision makers are looking for when evaluating these products for fit (I have been that person), what does "AI First" mean? I realize AI is the hype right now and it seems like most products have to pay the AI Tax (i.e. "Yes we're doing AI stuff so you should <buy/sell/fund/etc> our stuff"). But "AI" is a nebulous category, and when a product bills itself as "<Noun>-first", it sets up an expectation that <Noun> is fundamental to the product, i.e. if you stripped all other aspects of the product away, what's left at the end is <Noun>. But I have no idea what that means in the context of the current "AI" hype. Based on your demos, you've built a fairly standard looking ticket tracking tool that has some AI features. And those are features that every incumbent in this space started adding to their products years ago or are actively doing it now. I mention this not because I'm trying to say your product doesn't have value, but because the way you're positioning this doesn't make a lot of sense to me. As a prospective buyer, if I'm already using an existing tool, the moment I start digging deeper to know what "AI First" means, I'll find that what this really means is "Jira but with some AI features on top", which isn't very compelling when my <Vendor> account team has been telling me all about their new AI features that I can start using on all of my existing data as soon as I upgrade, no 6-18 month migration required. If I'm a frustrated customer of those products, AI is not the reason I'll be looking to switch, and I'd be far more likely to be interested in performance, extensibility, openness, integration capabilities, etc. Maybe that's not the type of customer you intend to target, but if you hope to reach them, I leave this as food for thought. Best of luck to you.
- koolhead 2y ago
  Someone had to call it out!!! thank you for that. Oh, the AI hype! It's basically just common sense wrapped in a shiny new package. Let's call quick filters 'AI' and be amazed, shall we? When the dataset is limited, what magical tricks can AI pull? Joining threads or conversations is just a fancy wildcard search. Where's the real optimization?
- parthacus 2y ago
  all that i wanted to say, only better. i am a zero-to-one guy and i get that this kind of positioning is often forward-looking, but i think that's what early-stage founders get wrong, especially if they aren't core whatever-noun they are anchoring to. if you consider all other incumbents in this space, they are all AI-driven. your differentiator could be AI only if you are core AI and have drawn up models for project or work management use cases. otherwise, just stick to whatever your differentiators are in the near-term and change positioning later when you are core AI. Taskade did this well. Notion is doing it well. they are all pivoting around AI without trading off whatever's their core.

163 points by harshithmul 2y ago

latchkey 2y ago

Finally got around to checking this out and got: "no healthy upstream"

Daviey 2y ago

Thanks for sharing, can you tell us more about the functionality that AI has in your product and what Cohere does for you, above the capability of OpenAI? Ta

harshithmul 2y ago
Current AI functionalities: 1. AI-generated Titles 2. Smart Delegation 3. Duplicate Detection 4. AI Summarization 5. AI filtering 6. Automated Triaging Cohere: To improve smart delegation, duplicate detection, and automated triaging, we integrate Cohere's advanced NLP capabilities, ensuring more accurate and efficient similar issue searches. We are bringing in more agents to delegate some of the work to them. 1. Code agent: This will help you in solving the small code fixes and small features but assigning issues to the agent and giving it instructions on how to solve them. 2. PRD agent: To help in PRD writing for the PM we'll add more agents for different use-cases going forward
- magicalhippo 2y ago
  We have several working at support who struggle with writing good issues due to dyslexia, lack of technical knowledge (domain experts) or similar. Was curious if the AI could assist them in a useful way. Sometimes they might poorly explain the problem, which module it pertains to or similar or similar, making it very unclear what exactly the issue is. I was thinking perhaps an AI component that could analyze what they said and "complain" if the AI detects key information is lacking, or perhaps just re-summarize what they wrote so it becomes more clear when they haven't supplied sufficient information.
  - harshithmul 2y ago
    That sounds exactly like something which we will be launching next week. We are working on an AI assist which will ask questions while creating issues in aspects like 1. If that can be broken into sub-issues 2. If it lacks information according to a template that's created in association with the label. For example: Label bug: You can explain in the template what is expected (Some deployment information, logs, screenshots etc.) and the AI assistant will help in ensuring those contents exist. We are also exploring if there are more such cases where AI can help. Do let us know your feedback on this once we launch

karpovv-boris 2y ago

[flagged]

darkhorse13 2y ago
Completely disagree. Their website is fairly unique, and looks really nice and usable. It's a bit "standard" with the gray, but that's fine if that's their branding.
- dewey 2y ago
  Unique? It looks like a Linear clone...but without the polish and design skills.
- meiraleal 2y ago
  It looks good indeed. Unique isn't the best way to describe it tho.
n3storm 2y ago
Imho, all too rounded buttons make them look like tags which has much less importance than controls.
hardwaresofton 2y ago
It's wild to see this posted on hackernews. I'm pretty sure hn has no problem with user traction.
kshri24 2y ago
Looks good to me.

wanderingmind 2y ago

If you are planning to monitise it through SaaS, might be worthwhile to change the license to AGPL from MIT.

harshithmul 2y ago
Thank you for your suggestion. You’re absolutely right; we are actively exploring licensing options, including AGPL, to ensure that our product remains protected. We value input from the community and are open to suggestions and assistance in making this decision. Our goal is to prevent unauthorized copying and resale of our product under different names while fostering a collaborative and innovative environment.
- zamalek 2y ago
  While the community may be a good source for ideas, you should retain an attorney. The community is not your lawyer. There's also the BSL. It specifically calls out competitive products. It automatically falls away for code older than a given time to another OSI license: https://en.wikipedia.org/wiki/Business_Source_License https://en.wikipedia.org/wiki/Business_Source_License. Per the Wikipedia article this still has issues: contributors are handing over their work for to you for free for that duration, they can't use their own work for profit. The AGPL does make your project extremely unattractive to competition, without affecting your contributors. The issue is that it is still possible to compete with you using it, so long as your competition releases all their code (i.e. infra, billing, etc.) under AGPL. I would personally go for AGPL because it will keep the worst offenders (Amazon, Microsoft) away from your code.
  - harshithmul 2y ago
    Understood, Thank you. Really appreciate all that information.
  - KolmogorovComp 2y ago
    Using BSL would make their code source-available but it wouldn’t be open-source anymore, unlike AGPL.

circularfoyers 2y ago

Do you support local LLMs? I could only see an ENV for OPENAI_API_KEY.

Manik_agg 2y ago
Hey another co-founder of Tegon here, currently we only support Open AI models but plan to add local models support with Olamma soon.
hrpnk 2y ago
There is also COHERE_API_KEY for the vector storage & search: https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/src/modules/vector/vector.service.ts#L30 https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61...
ranger_danger 2y ago
llama.cpp supports being an OpenAI API server, you would just need to change the URL in the Tegon source.

deepak_sozial 2y ago

how is it different from the mighty plane.so?

lawgimenez 2y ago
Why does plane.so look exacly like linear.app?
- tommoor 2y ago
  I think you can guess
  - lawgimenez 2y ago
    Yeah, I just searched some past discussions regarding plane. Not good
harshithmul 2y ago
Plane.so is indeed a great tool, and they emphasize creating an unopinionated platform that can be utilized by anyone. Our approach, however, is AI-first. We are focused on integrating multiple AI agents into our tool to assist stakeholders in various ways, including automating manual tasks, providing enhanced context, and even resolving issues end-to-end. Our goal is to leverage AI to significantly boost productivity and streamline workflows for our users.

deleted 2y ago

[deleted]

throwaway_fjmr 2y ago

I logged in around 2024-07-09 10:22 UTC, and I hope the stories in review don't get accepted. You might want to demo the product in a slightly less open way, though.

harshithmul 2y ago
Currently, our cloud service isn't publicly accessible, so we've been exploring the best way to demonstrate our product's features and functionality. To address this, we've created some demo credentials and a product instance for demo purposes. Additionally, we've taken a snapshot of a cleaner version of the product, which we refresh weekly. We will also explore more to see if there is a better way to do this.

faust201 2y ago

Would it be possible to run AI/ML on an existing jira/github large project (k9mail/KDE(gitlab) and show/prove this can be useful/better etc? Thanks

harshithmul 2y ago
We haven't yet modularized the AI features of our product. Currently, it's not possible to use the AI features on top of JIRA/GitLab. Our AI capabilities have achieved better accuracy and output because we have more control over the infrastructure and the product's foundations. Additionally, incorporating agents and managing their workflows require a distinct set of metadata and separate workflows, which we are still in the process of exploring.
- magicalhippo 2y ago
  Since one can self-host Tegon, do you have some importers working? That way I could import some Jira issues and see it in action on our own data. If you have an API to manage issues, that could work as well. Would need that anyway for custom build integration etc.
  - harshithmul 2y ago
    We are in the process of building those scripts. As we are working with companies for migration we started to improve these scripts to cover more edge cases. These should be out sometime soon. Otherwise, we have a public API to do CRUD operations for all important entities (issues, labels etc). We are working to get an openAPI spec once that is out we should have all the APIs added to our https://docs.tegon.ai https://docs.tegon.ai
    - magicalhippo 2y ago
      Sounds great, will keep an eye out.
- Aeolun 2y ago
  Can you give me an idea of what you are using AI for currently? Edit: Never mind, found the list you posted elsewhere.

itomato 2y ago

What evidence do you have that suggests auto-generated titles are better?

harshithmul 2y ago
We thought auto-generated titles could make life a bit easier. Creating the perfect title for every task can be tricky, especially when things get complicated. So, we added this feature to help with that. (This is also something I faced as a challenge while I was working in Airbyte the community does a great job at explaining the issues but we always have to edit the title to make it more crisp.) Right now, we’re using the product ourselves and trying it out with a few customers. We’ve noticed that for simple placeholder tasks, a straightforward title works just fine. But for more detailed tasks with longer descriptions, the auto-generated titles seem to work better. We’re still experimenting and gathering feedback to make it even better. Examples from our board: Description: - utils.py 228 : Failed to call LLM with the following error: BedrockException Invalid Authentication - An error occurred (UnrecognizedClientException) when calling the InvokeModel operation: The security token included in the request is invalid. Title: Feat: Investigate Salesforce cloud version error: Invalid Authentication Description: Triage ux bug - once i decline or accept a triage request, it re-directs me to issues screen. Ideal behaviour to be at the triage list view where you either show removing it from triage or highlighting that an action have been taken on this request. Title: Redirect user to Triage List after Accepting/Declining Request
- itomato 2y ago
  Lack of "crispness" in user titles is a tooling problem? Isn't this "wrinkly" technical detail lost?
  - harshithmul 2y ago
    We were experimenting if it could potentially help in taking that off the plate. Feedback taken we will work on improving that or taking a call based on how it performs.
- deleted 2y ago

CapeTheory 2y ago

IMO the absolute most important thing with a tool like this is performance. I have to sign in to a handful of cloud desktops each week and interact with customer Jira/Confluence/AzureDevOps/etc pages, and the big thing which kills my engagement is the app not being snappy enough. Doesn't matter how many of the features our Agile SAFe scrum wizard wants me to use, I'm not going to bother if there is too much friction. These apps inevitably require a lot of clicks, so latency becomes very noticeable.

harshithmul 2y ago
True performance is our priority. From the very beginning, we focused on ensuring that our app ran smoothly and quickly. To achieve this, we load all the data locally, allowing you to experience everything at lightning speed. Our background server keeps your data synchronized seamlessly between the server and the client, so you get the best of both worlds: speed and reliability.
- denysvitali 2y ago
  > True performance is our top priority The server is written in Node.JS
  - harshithmul 2y ago
    My bad. We focused on the performance on the front end currently, as said before we loaded all the data locally and kept the data synced in the background to make the interactions fast. We chose nodejs as that was easy for us to get started with. But definitely, if things get hampered we will start looking into it.
    - giovannibonetti 2y ago
      Good call. Front-end performance is often the bottleneck. Preloading most of the required data in advance is really helpful. Trello does just that and it is one of the snappiest web apps.
  - 2y ago

peterldowns 2y ago

First, congratulations on launching. I think people are so used to seeing beautiful products these days that it can be hard to remember how hard it is to make anything. Nice work! With that out of the way, here is some critical feedback: - What is the pitch that you made to YC that convinced them to back you? The market size just doesn't seem that large and I don't understand what will differentiate you from Linear (whose design language you seem to have ripped off, somewhat poorly.) This post and the current featureset is vague and does not seem like a significant improvement. What is the core problem you're solving and why is that valuable? Your launch post above describes a lot of "how" but not a lot of "why". - Why are you bothering to pretend to be "open source"? You're backed by YC and you'll make money selling access to the product on your "Tegon Cloud". If you're really going to be open-source, you need to make some significant improvements before anyone would consider contributing. Some documentation on how to self-host would be a good start. Look at all the environment variables in this dockerfile — which ones are necessary to run this service myself? https://github.com/tegonhq/tegon/blob/main/docker-compose.yaml#L55 https://github.com/tegonhq/tegon/blob/main/docker-compose.ya... - If you're going to be "open source", the quality of your codebase and engineering skills is going to be a deciding factor in whether or not you get outside contributors. Consider writing actual descriptions in your pull requests, describing what you've done and why. Here's a PR picked at random — this is bad engineering work and does not encourage others to contribute. https://github.com/tegonhq/tegon/pull/114 https://github.com/tegonhq/tegon/pull/114 My advice is that you drop the facade of being "open source", hire a designer, and do some actual user research to figure out where people are actually struggling with their ticketing systems. The features you're building (automatic title suggestion, thread summarization, and "find similar tickets") do not solve the problems that I have had with ticketing systems. They're small, potentially nice-to-have features that absolutely do not help me understand the core question for all engineering teams: who is doing what, how will they do it, why, and when will it be done.

peter_l_downs 2y ago
By the way, you've left the notiz.dev LICENSE file in your server code, probably you want to remove that. https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/LICENSE https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61... Separately, there seems to be a ton of unused or broken or dead code sprinkled throughout — for instance, in the auth code, I can't tell if you're doing basic email/password auth or using Supertokens and a third-party login via Google. You have code for both and some routes seem dead or missing. https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/frontend/src/modules/auth/signin-form.tsx https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61... Also, I mentioned the lack of documentation for how to run Tegon locally because your docs are entirely insufficient. The main docs page is just a README template. https://github.com/tegonhq/tegon/tree/main/docs https://github.com/tegonhq/tegon/tree/main/docs The quickstart guide has a broken link to instructions on how to self-host https://github.com/tegonhq/tegon/blob/main/docs/quickstart.mdx#self-hosted https://github.com/tegonhq/tegon/blob/main/docs/quickstart.m... The oss/local-setup guide is entirely empty https://github.com/tegonhq/tegon/blob/main/docs/oss/local-setup.mdx https://github.com/tegonhq/tegon/blob/main/docs/oss/local-se... The oss/deploy-tegon guide does not explain anything and the script it references seems out of date https://github.com/tegonhq/tegon/blob/main/docs/oss/deploy-tegon.mdx https://github.com/tegonhq/tegon/blob/main/docs/oss/deploy-t... I'm done looking at this project. I strongly recommend hiring the best engineer you can find as quickly as you can.

romanshamin 2y ago

[dead]

mort96 2y ago

> AI-first I would've been interested in an actual replacement for Jira/Linear, but I'm uninterested in an unreliable tool where I have to deal with hallucinations. Stop trying to cram this crap into every single software project.

codegeek 2y ago
Unfortunately, you need "AI First" to have any chance of VC funding for the past 2 years or so. They are probably keeping this in mind.
- mort96 2y ago
  That may be, but you need to not have "AI" or "AI-first" in your description in order to be an interesting product/project.
- giancarlostoro 2y ago
  The most obvious thing that should be done instead is to make an API spec that AIs can consume for your service, a common spec that if you target, any AI assistant can talk to freely. I feel like we're just over complicating things and burning money. Let the AI people burn their time and energy on the AI, let normal people build useful intuitive tools.

maximilianburke 2y ago

I'm getting a "no healthy upstream" error from the demo link.

harshithmul 2y ago
We started seeing people creating random issues we will get it back up after cleaning it a bit

hrpnk 2y ago

I was interested in how the duplicate detection of issues is working. It uses Cohere API for embeddings (full issue text) [1] and vector-based similarity search [2]. [1] https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/src/modules/vector/vector.service.ts#L66-L85 https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61... [2] https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c615510976b6025baef13/server/src/modules/vector/vector.service.ts#L125-L136 https://github.com/tegonhq/tegon/blob/158b54af8d6f7cf4195c61...

harshithmul 2y ago
We tried different approaches, we made a recent change where we started using cohere for re-ranking and embedding which did give really good results. Happy to create an account for you to try it out. harshith [@] tegon.ai

shafyy 2y ago

I don't know how to write this comment so it doesn't come off as unconstructive. But here you go. - "AI-first"? What does that even mean? Calling some API to auto-generate a title? Do you really think that a) this solves a big user problem and b) that Linear can't add that in two seconds if they wanted to? - Open-source and VC-backed? Please stop bull shitting me, and yourself. - What is your USP? That you're faster than Jira? Fine, but this is not 10 years ago and snappy tools like Linear exist (and I'm not even a fan of Linear). - elon@xyz.com? Really? Please use your time and talent for something else than this VC AI pipedream. Or don't, I'm just a rando on HN.

harshithmul 2y ago
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. We will be getting these out soon
mdeeks 2y ago
> that Linear can't add that in two seconds if they wanted to? FYI Linear has had this feature for a while. It works quite well.

johntash 2y ago

Do you think this would be useful for personal users as a todo/task management app? I have no chance of convincing work away from Jira, but I'm always on the lookout for a better personal task manager.

harshithmul 2y ago
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 https://github.com/tegonhq/tegon/issues/131

yamumsahoe 2y ago

linear set the bar so high but different projects have different needs.. i wonder how tegon and linear compare side by side.

haswell 2y ago

Having worked quite deeply with Jira and a host of other enterprise products that target this set of use cases, and having a pretty good understanding of what decision makers are looking for when evaluating these products for fit (I have been that person), what does "AI First" mean? I realize AI is the hype right now and it seems like most products have to pay the AI Tax (i.e. "Yes we're doing AI stuff so you should <buy/sell/fund/etc> our stuff"). But "AI" is a nebulous category, and when a product bills itself as "<Noun>-first", it sets up an expectation that <Noun> is fundamental to the product, i.e. if you stripped all other aspects of the product away, what's left at the end is <Noun>. But I have no idea what that means in the context of the current "AI" hype. Based on your demos, you've built a fairly standard looking ticket tracking tool that has some AI features. And those are features that every incumbent in this space started adding to their products years ago or are actively doing it now. I mention this not because I'm trying to say your product doesn't have value, but because the way you're positioning this doesn't make a lot of sense to me. As a prospective buyer, if I'm already using an existing tool, the moment I start digging deeper to know what "AI First" means, I'll find that what this really means is "Jira but with some AI features on top", which isn't very compelling when my <Vendor> account team has been telling me all about their new AI features that I can start using on all of my existing data as soon as I upgrade, no 6-18 month migration required. If I'm a frustrated customer of those products, AI is not the reason I'll be looking to switch, and I'd be far more likely to be interested in performance, extensibility, openness, integration capabilities, etc. Maybe that's not the type of customer you intend to target, but if you hope to reach them, I leave this as food for thought. Best of luck to you.

koolhead 2y ago
Someone had to call it out!!! thank you for that. Oh, the AI hype! It's basically just common sense wrapped in a shiny new package. Let's call quick filters 'AI' and be amazed, shall we? When the dataset is limited, what magical tricks can AI pull? Joining threads or conversations is just a fancy wildcard search. Where's the real optimization?
parthacus 2y ago
all that i wanted to say, only better. i am a zero-to-one guy and i get that this kind of positioning is often forward-looking, but i think that's what early-stage founders get wrong, especially if they aren't core whatever-noun they are anchoring to. if you consider all other incumbents in this space, they are all AI-driven. your differentiator could be AI only if you are core AI and have drawn up models for project or work management use cases. otherwise, just stick to whatever your differentiators are in the near-term and change positioning later when you are core AI. Taskade did this well. Notion is doing it well. they are all pivoting around AI without trading off whatever's their core.