Graphite helps teams on GitHub deliver higher quality software, faster.
Users generally appreciate Graphite for its AI-powered capabilities, especially in areas like data conversion and handling complex data structures in documents. However, there are complaints about its performance in version control, particularly in managing stacked pull requests, which some find cumbersome. Pricing sentiment is not prominently discussed, indicating it may not be a primary concern for most users. Overall, Graphite appears to have a positive reputation for its AI features, but with room for improvement in version control functionalities.
Mentions (30d)
1
Reviews
0
Platforms
2
Sentiment
0%
0 positive
Users generally appreciate Graphite for its AI-powered capabilities, especially in areas like data conversion and handling complex data structures in documents. However, there are complaints about its performance in version control, particularly in managing stacked pull requests, which some find cumbersome. Pricing sentiment is not prominently discussed, indicating it may not be a primary concern for most users. Overall, Graphite appears to have a positive reputation for its AI features, but with room for improvement in version control functionalities.
Features
Use Cases
Industry
information technology & services
Employees
81
Funding Stage
Series B
Total Funding
$95.2M
I Renovated My Apartment With AI. Here's What Came Out of It
Spoiler: not a single visible cable, not a single piece of furniture moved twice. When I started, I had an apartment and dimensions from the building blueprint. No designer. No clear idea where to go. But there was a desire to make something that would turn a standard apartment in a high-rise into a place of power — a place comfortable to live and work in. Instead of a designer, I took Claude. How it all began The first conversation wasn't about furniture or wallpaper. It was about direction. I didn't know what I wanted. I knew what I didn't want — kitsch, heavy classics, excessive decoration. We worked through options together. Scandinavian minimalism. Japanese wabi-sabi. Loft. Modern classic. The AI broke down each style by character, materials, color logic. Not "this would suit you," but "here's what this means, here's what this requires, here's what you'll get." In the end I arrived at Scandinavian for the bedroom. Warm, light, calm, with one deliberate accent behind the headboard. The living room–kitchen — loft with a red thread running through the whole space, because the furniture there was already concrete-grey with red niches and replacing it wasn't on the table. The hallway and corridor — neutral grey, as a transition between two characters. Three zones, three moods, one logic. The bedroom This was the most detailed conversation. A room with one window, one door, three free walls. Together we came up with: an accent wall behind the headboard with golden geometric lines, the other three walls in cream from the same collection. Tone on tone, different saturation, same texture. The seam between walls reads not as a boundary but as gradation. White matte furniture with black hardware. A wardrobe with a top cabinet almost to the ceiling. Mirrored doors reflect the accent wall — the golden lines are present even where they physically aren't. Then came the centimeters. The AI calculated. Adding up wardrobe depth, gaps, bed width, nightstands, dresser. Checking that everything fits. Whether the wardrobe door opens without hitting the nightstand. It even accounted for the arc of opening — that's a whole separate half-page story with mathematical formulas. By the end I had not "approximate distances" but specific points. Where to mount the light. Where to place the bed. Where to cut a network outlet into the baseboard. At what height to mount the TV unit so that watching half-lying down would be comfortable — that was calculated too, through mattress height plus pillows plus eye position. The living room Different approach. Here there was already furniture that wasn't being replaced: concrete-grey, red niches, black desk, grey sofa. The task — give the space one wall that would tie it all together. We decided: accent wallpaper behind the sofa, on the longest wall. Red-black-grey circles. Red from the furniture niches, black from the desk, grey from the concrete furniture — the wallpaper literally collects the room's palette into one pattern. By the way, an unexpected moment happened with this wallpaper: it turned out to have glitter, which only added character to the room — it plays so beautifully at sunset. The fridge against the same wall is white. It was bought six months ago, and buying a new one wasn't an option. The solution — a vinyl sticker. In red-black geometry. The fridge stops being a white blot and becomes part of the wall. Between the sofa and the kitchen zone — a floor lamp with shelves in a black metal frame. And on the top shelf, an object with character — a replica of an iconic artifact from a favorite horror film. Yes, the Lament Configuration from Hellraiser. A personal thing with a story. Why not? The hallway and corridor Grey wallpaper with a vertical tone-on-tone stripe along the entire perimeter. Grey — a neutral buffer between the red-black living room and the cream bedroom. The entryway unit in oak and graphite. Warm wood against cold grey gives the temperature contrast needed. The vestibule is small, the unit doesn't take up the whole wall — the remaining meter of free wall is for a shoe bench, above which there will be either a mirror or some poster. By the way, ideas for posters Claude also suggested — both within the renovation discussion and in other conversations connected to my work and hobbies. The through-line Between all three spaces there are recurring elements: Black hardware — bedroom wardrobe handles, black curtain rod, black floor lamp frame in the living room, black handles on the entryway unit. Geometry — lines on the bedroom accent wall, circles on the living room accent wall, verticals on the hallway wallpaper. Warm base — cream tones in the bedroom, warm wood in the entryway. These aren't accidental coincidences. This is the logic we built in dialogue. What the contractors got The most valuable thing about all this work — I handed the contractor not "well, roughly in the middle" but coordinates accurate to the centimeter. Where to m
View originalWhy 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