Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • This is what was for looking for. I need a visual surface to plan agentic feature development workflow. Don't you mind if I make Paca integration with the AI agentic Go runtime I'm developing? your OpenHands concept with container per agent seem little heavy. I will start from WASM plugin, but in perspective, I would like to make a port replacing the OpenHands on services/ai-agent level.
    by denn-gubsky
  • That sounds absolutely amazing! I'd love to see that integration.

    In fact, you are more than welcome to work directly on a branch in the Paca repository and contribute to the community with me. I'd be thrilled to collaborate!

    If you'd like, feel free to connect with me on LinkedIn: https://www.linkedin.com/in/pikann22

    by pikann22
  • I think this is capturing the current need - solo vibe engineers that need structured task tracking. Since I pop between machines for various reasons, I tend to keep this info in the project itself, but an MCP server could go a long way. Tracking this project
    by smrtinsert
  • Thanks for having a security policy

    https://github.com/Paca-AI/paca/security

    However I'm getting a 404

    https://github.com/Paca-AI/paca/security/advisories/new

    (You need to enable private security advisories: https://docs.github.com/en/code-security/how-tos/report-and-..., really not sure why GitHub made it opt-in only)

    by eranation
  • Thank you! I didn't realize it was opt-in. I've enabled it now, so the link should work properly
    by pikann22
  • Backlog.md the project: tasks live in your repo, atomic and race free
    by eisbaw
  • I guess everyone uses 20% percent of Jira - just a different 20% ... [1]

    We're using GitHub for everything here, but was using Jira as an email first helpdesk.

    Was hoping this was that - but apparently not at all.

    We almost went with libredesk - but it's a little too simple (no merging tickets?). We're giving FreeScout a go - looks like we might need the oauth2 plugin to work with o365 mail ...

    [1] https://www.joelonsoftware.com/2001/03/23/strategy-letter-iv...

    > A lot of software developers are seduced by the old “80/20” rule. It seems to make a lot of sense: 80% of the people use 20% of the features. So you convince yourself that you only need to implement 20% of the features, and you can still sell 80% as many copies.

    > Unfortunately, it’s never the same 20%. Everybody uses a different set of features.

    -- Joel Splosky

    by e12e
  • I'm using GitHub issues and GitHub Projects with `gh` cli and I find it works well, though what I really like about this is your project level chat. I find myself having to come back to a project level session often. May give this a try, just hesitant to put it on something that's in-flight with already lots of stuff, will have to be a net new project.
    by hmokiguess
  • Thanks! Glad you like the project-level chat. Starting with a fresh project is definitely the safest bet to see if the workflow fits you. If you ever do try it out, I'd love to get your feedback!
    by pikann22
  • I can't believe you guys give this for free. I was considering buying "Linear", now I just saved 10$/month with this. Thank you so much
    by tom-wal
  • I've been trying keeping an eye on open source issue trackers/project managament tools I can self-host -- with good cli/mcp capabilities. So quite happy to see this as I feel there isn't a lot! (currently also using gh issues) will check it out!
    by sambucini
  • Specifically on the AI side, how does it compare to beads?
    by kamikazechaser
  • You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP.

    This is what I did with this project https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.

    by _pdp_
  • > You can take it a step further and strip out the frontend.

    You can take it a step even further and strip out all the code too!

    by re-thc
  • I need it, I want it. Why speaking out for me?
    by subscribed
  • "Nobody needs it"

    "Fits me well"

    So maybe don't speak for everybody?

    by spiderfarmer
  • I like the direction! But why stop with CRM functionality with very limited schema for tasks on the headless when OP has a lot more to offer there? Why stop at CRM plus Project Management then? Why not also schemas for ERP, HR, finance tools and all other business software? And we even bother with a custom made API when PostgreSQL and PostgREST could reduce the full thinking to the database schema?
    by mcbetz
  • What are people's workflows these days?

    As I use claude more and more I've started using git worktrees, one branch per worktree per PR, with possibly multiple agents working in each worktree at the same time on different aspects. And I manually instruct those agents. Like Emdash/Cursor/Zed. Sometimes I review code locally, sometimes agents push and I review in GitHub, no clear system yet. (jj seems promising, but Zed doesn't seem to support jj as well as git, so have delayed looking at it.)

    But Paca is hinting in another direction where the agents are more in control of the branches/worktrees to use and are created by the agent? What tooling is used to support such flows? Would people use GitHub with Paca or is GitHub redundant as well.

    by dagss
  • Have custom slash commands in forgejo that spawn an agent using deepwhale which creates a branch, then commits and opens a PR when done.
    by mzhaase
  • How much are worktrees benefitting you? If I can describe the work so clearly that it can be done in parallel, I find Claude can typically one shot so parallel work isn't needed.
    by smrtinsert
  • Gh issues works surprisingly well as an agent board. Labels for state, one issue per feature. The part i haven't figured out yet is how to know when the output is actually done vs just "looks done" to the agent.
    by flo_r
  • This is pretty much my flow as well. Haven't gone beyond managing three work trees in parallel. It's nice being able to test locally against multiple work trees -- one is at 3000, then 3001, etc.
    by joshoink