1,357 results for work lab · 2.344s

News for “work lab”
19 results • 2336 ms server time
Moozonian News
news.ycombinator.com• 6d ago• 1 min read
Continue coding agent is dead. Alternatives?It was nice to use on vscode with offline Ollama but today notices it is not updated anymore. So, alternatives you use?From github:"Note: The continuedev/continue repository is no longer actively maintained and is read-only for all users."From continue.dev:"Continue has joined Cursor Continue was acquired by Cursor. Our mission was always to ensure developers are amplified, not automated, and that commitment carries on in the work ahead.It was an honor to build with the Continue community. Thank you to each and every one of you who helped us create a pioneering open-source coding agent.What we built together pushed the boundaries of what AI developer tooling could be, and our open-source codebase remains freely available as a foundation for others."
Advertisement
Moozonian News
ozbrain.com• Aug 21, 2026• 1 min read
Show HN: OzBrain, a shared brain for knowledge between agents and your teamI think agent-first chat interfaces will be a primary software modality and busy dashboard/UI will go away. I’m not sure who exactly wins it, but I want my knowledge to grow/go with me.A lot of the “knowledge” ie research, analysis, reasoning will be done by agents as the primary user. Our current notes tools & tasks management systems were built for humans… I don’t care what the 17th thing on my bug backlog is. I want to conduct agents that can execute for me and do great work.What I built OzBrain to do: + Create a central place for agent reasoned knowledge to live + Be agnostic about what apps/agents connect to it + Capture everything and track it so I can audit it + Enable teams, collaborators or partners to share brains + Handle conflicts so many agents in the same article doesn’t blow up + Refactor knowledge into more token friendly chunks and map the index well + Close the knowledge loop so new thinking supersedes old thinking across the corpus. Don’t erase, depreciate and link +
Moozonian News
news.ycombinator.com• Aug 21, 2026• 1 min read
Windmill.dev is not "fully open-sourced (AGPLv3)"I think Windmill.dev (https://github.com/windmill-labs/windmill) is really cool, and fully support their desire to be paid for their work.However, their README says:> “Windmill is fully open-sourced (AGPLv3)…”But their LICENSE says:> ... The files under backend/ are AGPLv3 Licensed, except any snippets of code under the compile flag ‘enterprise’. Those snippets and files are under a proprietary and commercial license. Private and public forks MUST not include the proprietary/commercial code mentioned above.I dove deeper into the code, there are around 300 files in the codebase that contain references to enterprise or private features, so it's not a clearly separated directory that can just be removed.They have 1.1k forks of their repository that I can see on Github, and I doubt all of them took the time to strip the proprietary code to comply with the license.So at this point, it feels like a licensing trap for anyone that clicks the fork button on Github or is attracted by the AGPL li
Moozonian News
traccia.ai• Aug 21, 2026• 1 min read
Show HN: Traccia - Observability, Runtime Control & Audit for agentsAI applications are becoming agents, which has started to take autonomous decisions. There are plenty of tools and platform available to trace, and observe what an agent or llms calls does. They are good in what they do, but tracing and observability isnt enough for AI agents era. We need a solution that can help you observe, evaluate, create run time policies to govern and finally audit the actions of the agent. We built Traccia to solve this problem. The good part, all of these can be achieved by just writing few lines of code. Traccia has an open-sourced sdk that can work with your existing observability tool like grafana, tempo, jaeger, etc. In case you need more than just observability, Traccia provides the platform to evaluate, control and audit the agents. The platform is easy to use. The product's documentation is quite extensive. It is also cloud vendor and framework agnostic. Traccia is being built by an Indian start up ,based out of Bengaluru. We are running a 3 months free
Advertisement
Moozonian News
github.com• Aug 21, 2026• 1 min read
Show HN: A coding-agent workbench built around Matt Pocock's coding workflowRepo URL: https://github.com/ticketry-hq/ticketryTicketry helps you execute a coding workflow using terminal agents. We run coding agents on tmux-based durable terminals. Each idea you have can be written down, and we take it through grilling, speccing, splitting it into tickets, implementation, and review. The workflow is based on Matt Pocock's workflow.Please have tmux installed for the terminal to work. Also go into your privacy settings and say "open anyway". I haven't signed it yet.Note: This is not a collaboration effort with Matt; it is just uses the skills.
Moozonian News
news.ycombinator.com• Aug 21, 2026• 1 min read
Ask HN: Do teams really need to use GitHub?Enterprises can self-host, sure. Open source projects uses it for the the network effects of GitHub. But why does a small software team need to use GitHub?I understand the ecosystem argument. Once you've got your repos, CI/CD, PRs, code reviews, packages, integrations, etc. all wired into GitHub, moving everything is a pain. But Git itself is distributed, and GitHub has a pretty open plugin/integration system. There are also perfectly capable alternatives like GitLab, Bitbucket, Forgejo, Gitea, SourceHut, etc.So what is the actual thing that makes a 10–20 person software company stick with GitHub? Is it mostly switching costs? The ecosystem? Developer familiarity? Something else? And if you were to start a project today, would you still go with GitHub?And a slightly more personal question.I've had a rough idea for what a new GitHub could look like if it were built specifically for software that is increasingly being written by AI agents, and specifically for companies rather than open-
Advertisement
Moozonian News
github.com• Aug 20, 2026• 1 min read
Show HN: Icebug-format: immutable, interoperable graph standardMost graph analytics packages have a mutable graph implementation that uses a heap allocated vector to store the graph. It works for toy graphs. But if you're loading a billion edge graph using G.add_edge() it's going to take a while.We don't need to invent new standards. Such interoperable, immutable memory standards already exist: Apache Arrow and Compressed Sparse Rows (CSR). CSR is widely used in scipy, cugraph and columnar graph databases among others. Both on CPUs and GPUs.icebug-format combines both into a on-disk standard based on Apache Parquet and an in-memory format based on Apache Arrow.Bindings available in many popular languages including python, typescript and rust.The package ships with convenience scripts to convert flat tables such as vertex.parquet and edges.parquet to this format in RAM/disk constrained environments.Sample graphs: https://huggingface.co/datasets/ladybugdb/ldbc-csr/tree/mainConverted from: https://ldbcouncil.org/benchmarks/graphalytics/datasets/Large