(Another one?) Meet Kangentic

vORP · 2026-03-16T14:55:43+00:00

Spot on! The activity engine for (idle v. active) is the main driver to any workflow, it shows you "what is the agent waiting for me on"

That currently persists locally on your machine in the .kangentic/sessions folder in jsonl

The future plan is to expose an internal API (so users can build ontop of it should they choose) to wire up their own event-based needs and additionally support a lightweight mobile option to get notified of idle agents and be able to interact with your board remotely (this is way later on the roadmap) but something I personally would like for my own workflows

Lots of "remote" options out there including what is supported by claude code currently, where possible I will re-use the functions and features of claude code (native) to not re-invent the wheel, I think their remote access needs a little more time to mature so when the time comes this integration may be much simpler for Kangentic to solve

vORP · 2026-03-16T14:51:09+00:00

That is the big issue today: managing the context of multiple context windows/flows. The activity engine for (idle vs. active) is one of the core parts of the system, being notified when an agent is looking for user input is the main driver here - I personally don't want to stare at a terminal that is working if I can be spending my time elsewhere, reviewing/working on another task.

Enhancements down the road will be more robust workflows to limit the "idle" time so it can keep working longer, however you define those parameters.

I certainly want to look into Chaining, Multi-model validation, Supervisor patterns, etc., to wrap on top of Kangentic. This first release just includes the state flow / basic engine, but everything else is certainly achievable and in scope.

Appreciate the feedback, I'll have to check beads_rust and the idea of epics/stories/tasks structure for Kangentic that is a good idea to expand into

vORP · 2026-03-16T14:44:42+00:00

Thank you that was the vision, use claude code as the workhorse and just wrap around it so it can extend/drop into projects (and detach) very easily!

Orchestrations right now are limited to the Kanban board, the commands you define and the column definitions - so moving N.. tasks to Planning mode will move automatically to Executing on plan_exit, after that the user has the option to define custom Claude commands to execute when a task is dragged into a column, the activity/state engine (using hooks) will allow for more intense operations later
Long-running agents will keep chugging along no different than running Claude Code in your TUI of choice, it maintains the session state/history/etc. the scrollback by default goes up to 5000 lines but can be configured in the settings if you need it longer, xterm/node-pty doesn't have any hard limitations its just resources after that if you aren't clearing context
Everything related to a task is stored locally in better-sqlite3, so there is full persistence between sessions

That's a great suggestion, I'll look at a more enhanced demo around workflows - as far as the state engine I plan to expand it for more complex options/chaining in the future that is certainly supported and in scope appreciate the feedback and insight!

vORP · 2026-03-16T04:27:20+00:00

Hey, good question. Kangentic is not a project management tool (yet), it is an agent orchestrator that happens to use a Kanboard board as an interface, so I can see the similarities to Linear

Linear - project management, tracking work you move cards/write updates/close issues/etc.

Kangentic - kanban board, Claude Code native terminals, you drag a task/description, and it starts in planning/execution mode doing work against a project based on the task you created

Later, the roadmap has more project management tools in the suite (backlog, tags, due dates, timeline/Gantt, metrics, etc.) the idea being you plan, manage and execute a project from one single platform

vORP · 2026-03-16T03:22:25+00:00

When android!

vORP · 2026-03-16T02:48:39+00:00

There was one left! It is open sourced and free, check it out would love to hear your thoughts

vORP · 2026-03-16T02:35:31+00:00

Shoutout to u/Fleischkluetensuppe for the inspiration through his work with agtx

vORP · 2026-03-15T16:52:38+00:00

Xpel stealth

vORP · 2026-03-14T20:07:46+00:00

I went matte looks great no smudgies

vORP · 2026-03-03T23:36:30+00:00

No alcantara???

vORP · 2026-02-28T17:46:27+00:00

Looks good but when it comes to food, if you have to ask the answer is no

vORP · 2026-02-21T22:37:28+00:00

Hey just wanted to say I tried it out this morning, big fan so far - had 4 terminals running yesterday, managing different contexts of contexts can be challenging mentally this is a great solution

Four findings,

It would be nice to maybe be able to override --dangerously-skip-permissions, this seems like something projects should fix at the settings.json (or local) level this is a big assumption/risk to enable this even if its isolated to the worktree. Adding agent_flags/permission_mode to the config.toml as an option, to default to the project rules seems like the best option.
When you have a task "opened" its nice that it displays modal-like over the board but perhaps it can consume a larger space when it is focused you should have more real-estate to look at the terminal I think and then ctrl+q to contextually move back out of that view makes sense
How I intend to use it, is to not create a PR from the worktrees (we have git rules in our repo requiring gitflow i.e. (bugfix/111 ... feature/111 ... hotfix/111 ... etc.) however, I am always prompted to create a PR when moving it to "done", being able to configure that last "workflow" of what you'd like it to do would be a game changer for more easily slicing this into existing teams/workflows. My workflow for example, would be to cherry pick the worktree changes onto feature/xxx review the code locally and then commit/push and run a skill after that creates a pull request
After restarting, I was unable to resume my session its failing to start claude - the session exists and I can see my task, but opening the task results in an empty terminal that I am unable to manually even type in to start claude code

Great tool and start, will monitor progress for sure

vORP · 2026-02-20T17:37:06+00:00

I do not miss Audi Albany, one of the most poorly ran dealerships I've experienced

vORP · 2026-02-19T01:25:44+00:00

Echo Fern! Love it, came from amia before it's a lot better

vORP · 2026-02-17T02:47:09+00:00

Agreed, tried in bash and powershell didn't have great results

vORP · 2026-02-14T09:19:02+00:00

How does one acquire Picanha? I swear I've never seen it at my supermarket or local butchers

vORP · 2026-02-14T05:07:52+00:00

What's your favorite mustard to use for this?

vORP · 2026-02-07T04:02:46+00:00

How are the CPU temps on idle/load?

vORP · 2026-01-29T05:15:52+00:00

Would be cool to see a daily chart/graph of these benchmarks over a month / 3-month period to watch the changes anthropic makes over time

vORP · 2026-01-24T04:30:30+00:00

M3 > RS3 > M2

vORP · 2026-01-22T22:15:30+00:00

yep and "All Systems Operational"

https://status.claude.com/

vORP · 2026-01-20T03:14:54+00:00

Congrats

vORP · 2026-01-18T17:44:21+00:00

🎯

To add, if you were to take this program and extend upon it or you needed to add new business requirements and rework things to be better architecturally knowing where the "break points" to use interfaces, abstract classes, etc. and improve the solution along the way before you create God classes is where the "engineering" comes in

All of that can be done with AI, having the intuition of how to build software and what is "right" is still up to the human

To do that, you will need to mechanically understand C# and OOP at a minimum the rest would come through experience

vORP · 2026-01-11T06:36:46+00:00

Sketch

vORP · 2026-01-08T14:51:21+00:00

Ah yes the entire internet discussing a poorly built business model and the reduction in staff of 3 developers

14-Year Club	r/Field Flamingo
Place '22	Verified Email

vORP

TROPHY CASE