Field notes + complementary DLC for a two-consumer (local operator + CLI IDE) setup
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- sqlite
- Domain
- documentation
Research direction
The issue points to the public pack at CynicalTyr/codegraph-split-horizon and mentions serve --mcp --path, but it requests no specific change and names no files or tests in this repository. Read the issue and linked pack to understand the proposed ecosystem link; there is no defined implementation or test that would establish done.
Written by the indexing model from the issue text.
Description
Hi Colby, CodeGraph is the engine I run daily, thank you for it. I did not replace it.
I ended up with two consumers on one box: an unattended local autonomous loop (on-box models, tools) and a CLI IDE architect on MCP. One serve --mcp --path. Two SQLite graphs. Writer UID has to match the database owner. include is not a whitelist on a home directory. Empty explore on mapped scripts is expected. Extra corpora stay projectPath. Slow-disk first index needs CODEGRAPH_NO_WATCHDOG. A CIFS share of another host is not a local graph. I wrote that down as installable mods (00–14) sitting on your own @colbymchenry/codegraph 1.6.0 engine src/ untouched.
Public pack: https://github.com/CynicalTyr/codegraph-split-horizon
This is a courtesy note, not a request to merge my overlay or to take a huge docs dump 💩 PR. If an ecosystem link is useful, that is your call. If it is noise, feel free to close this.
Credit stays with you for the indexer. I just paid the WAL tax so the next person does not have to invent the same problems I had locally with multi agents on one box using multiple Unix administrative terminals.
- Dominant language
- C
- Stars
- 73.2k
- Forks
- 4.7k
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 418
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from colbymchenry/codegraph
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
colbymchenry/codegraph#2634 ·
Maintainers usually reply within 1 day
-
Windows: bundled Node v24.16.0 can abort at exit (nodejs/node#56645); please bundle Node >= 24.20.0Possibly taken @Ancienttwo claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
colbymchenry/codegraph#2617 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 72/100
colbymchenry/codegraph#2482 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
colbymchenry/codegraph#1900 · 2 comments · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
colbymchenry/codegraph#1700 ·
Maintainers usually reply within 1 day
All issues in colbymchenry/codegraph
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OpenPrinting/cups#1772 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
antoxa2584x/nfsu2-sw#44 · 1 reaction ·
Maintainers usually reply within 1 day