Graphite helps teams on GitHub deliver higher quality software, faster.
Users generally appreciate Graphite for its advanced AI capabilities, citing enhanced productivity and efficiency in code creation and management. However, there are complaints about version control functionalities, with some users expressing frustration over its handling of PR stacking. Sentiment around pricing is not mentioned explicitly in the reviews or social mentions. Overall, Graphite holds a solid reputation for innovation but could improve in specific workflow integrations.
Mentions (30d)
1
Reviews
0
Platforms
2
Sentiment
0%
0 positive
Users generally appreciate Graphite for its advanced AI capabilities, citing enhanced productivity and efficiency in code creation and management. However, there are complaints about version control functionalities, with some users expressing frustration over its handling of PR stacking. Sentiment around pricing is not mentioned explicitly in the reviews or social mentions. Overall, Graphite holds a solid reputation for innovation but could improve in specific workflow integrations.
Features
Use Cases
Industry
information technology & services
Employees
89
Funding Stage
Series B
Total Funding
$95.2M
Why Is Table Extraction with VLM Models Still Challenging? [D]
Hey everyone, I’m struggling to find a good approach for converting PDFs to Markdown (especially for financial data). The main challenge is handling borderless tables and tables with more than 5–6 columns. I’ve tried docling, graphite-docling, marker, etc., but haven’t found a solid open-source solution. The only thing that works well so far is LandingAI (but it’s paid). Does anyone know of a good open-source alternative? TIA! Sample: https://preview.redd.it/tajjcvjt5jyg1.png?width=959&format=png&auto=webp&s=8d04c5e946ab361bfef08021f79d106ab62a07cd https://preview.redd.it/lhpwnbty5jyg1.png?width=630&format=png&auto=webp&s=8dc0475a32b89ce7f8107f3940fd3eb6b0896a3a submitted by /u/No_Stretch_5809 [link] [comments]
View originalAgents seem to suck at version control
My company’s workflow involves PR stacking where we stack a bunch of small PRs on top of each other, so PR reviews are manageable for humans (rather than reviewing a huge singular PR). However, it feels like agents are horrible at doing PR stacking. My typical workflow is that I lay out a plan with the agent, plan out the contents of each PR and have the agent work through the PRs. Creating the initial stack is fine, but everything goes wrong when the agent either runs into a merge conflict in the middle of the stack, or tries to mess with the stack structure. Here are a few prompts that I use: Assume we have a PR structure as follows: (8 is on top of 67, 69 on top of 68, ...). In other words: main <- 67 <- 68 <- 69 ... “I want you to have PR 67 on top of PR 69 instead of PR 68.” Result: Somehow, the agent will touch PRs that I NEVER MENTION to it and now PR 67 is somehow based on PR 71 and PR 69 and 68 are independent PRs. “PR 67 has a merge conflict. First validate the existing stack structure, then make changes to the PR, then submit the stack” Result: Agent solves the merge conflict. Agent tries rebasing PRs 68, 69 … and encounters merge conflicts there. Agent resolves merge conflicts by running git push force origin and messes up, either rebasing on the wrong thing or forgetting to sync origin with local. The worst part is that the agent uses git push origin —force, which wipes commits. This command is necessary if you want to resolve rebasing issues. But you’re effectively losing the ability to revert back in time. I’ve been using graphite and I use the graphite skill that the company gave me and the agent almost always still messes up. I tried looking for tips online and I have found almost nothing on how to have agents avoid messing up PRs. I’m honestly so frustrated and I’m not sure if anyone else has found any luck. submitted by /u/RewardVegetable5701 [link] [comments]
View originalGraphite uses a subscription + per-seat + tiered pricing model. Visit their website for current pricing details.
Key features include: Graphite CLI, Pull request inbox, Graphite Chat, Merge Queue, Insights and reports, Start a stack, Keep stacking, Visualize your stack.
Graphite is commonly used for: Streamlining code reviews by utilizing Cursor Cloud Agents within PRs., Enhancing collaboration among team members through Graphite Chat., Managing multiple pull requests efficiently with the Merge Queue feature., Visualizing the development stack to understand project progress., Generating insights and reports for better decision-making., Responding to feedback directly within the PR for quicker iterations..
Graphite integrates with: GitHub, Slack, Jira, Trello, CircleCI, Travis CI, GitLab, Bitbucket, Asana, Zapier.
Reviewing a PR in Graphite
Jan 21, 2026
