<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
		<title>The Rezee blog</title>
		<link>https://rezee.app/blog</link>
		<description>Education, engineering deep-dives, honest comparisons, and product notes from the team building Rezee - the unified workspace for everything your team ships.</description>
		<item>
			<title>Highlighting a 5,000-line diff without freezing the tab</title>
			<link>https://rezee.app/blog/async-shiki-diff-tokenization</link>
			<guid>https://rezee.app/blog/async-shiki-diff-tokenization</guid>
			<pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate>
			<description>How Rezee's diff viewer syntax-highlights large diffs without a frozen frame - Shiki tokenization is synchronous CPU, so the trick isn't going off-thread, it's chopping one 305ms block into 125 sub-5ms bursts, measured.</description>
		</item>
		<item>
			<title>Drag a card, write one row - fractional indexing on the issues board</title>
			<link>https://rezee.app/blog/fractional-indexing-drag-reorder</link>
			<guid>https://rezee.app/blog/fractional-indexing-drag-reorder</guid>
			<pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
			<description>How Rezee persists Linear-style drag reordering - the lexicographic midpoint algorithm behind issues.rank, measured key growth under adversarial dragging, why float ranks die at exactly 53 moves, and a 5,000x difference in rows written.</description>
		</item>
		<item>
			<title>Inside Rezee - agents as teammates, not features (AI &amp; Agents)</title>
			<link>https://rezee.app/blog/inside-rezee-ai-and-agents</link>
			<guid>https://rezee.app/blog/inside-rezee-ai-and-agents</guid>
			<pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
			<description>The thinking behind Rezee's AI &amp; Agents layer - agents as workspace members with scoped access and full attribution, working assigned issues, CI failures, review, and doc drafts, with humans holding the gates.</description>
		</item>
		<item>
			<title>Inside Rezee - from push to production in one layer (Code &amp; Ship)</title>
			<link>https://rezee.app/blog/inside-rezee-code-and-ship</link>
			<guid>https://rezee.app/blog/inside-rezee-code-and-ship</guid>
			<pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
			<description>The thinking behind Rezee's Code &amp; Ship layer - standard git over HTTPS and SSH, inline pull request review, protected branches, and YAML pipelines with isolated steps and live logs.</description>
		</item>
		<item>
			<title>Inside Rezee - chat that knows what you're talking about (Discuss &amp; Document)</title>
			<link>https://rezee.app/blog/inside-rezee-discuss-and-document</link>
			<guid>https://rezee.app/blog/inside-rezee-discuss-and-document</guid>
			<pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
			<description>The thinking behind Rezee's Discuss &amp; Document layer - channels and threads beside the work, PR and issue unfurls that stay live, and one search across chat, docs, code, and issues.</description>
		</item>
		<item>
			<title>Inside Rezee - why specs live next to the code (Ideate &amp; Design)</title>
			<link>https://rezee.app/blog/inside-rezee-ideate-and-design</link>
			<guid>https://rezee.app/blog/inside-rezee-ideate-and-design</guid>
			<pubDate>Wed, 22 Jul 2026 00:00:00 GMT</pubDate>
			<description>The thinking behind Rezee's Ideate &amp; Design layer - a block editor with live presence, RFC templates and numbering, live references, and specs that live next to the code they describe.</description>
		</item>
		<item>
			<title>Inside Rezee - planning that closes itself (Plan &amp; Track)</title>
			<link>https://rezee.app/blog/inside-rezee-plan-and-track</link>
			<guid>https://rezee.app/blog/inside-rezee-plan-and-track</guid>
			<pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
			<description>The thinking behind Rezee's Plan &amp; Track layer - issues with owners and workflows, projects and milestones, and pull requests that close issues automatically so the tracker stays truthful.</description>
		</item>
		<item>
			<title>A service mesh in one HTTP header - and the measured case against mTLS</title>
			<link>https://rezee.app/blog/one-header-service-mesh</link>
			<guid>https://rezee.app/blog/one-header-service-mesh</guid>
			<pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
			<description>How Rezee secures service-to-service calls with a shared-secret header instead of mutual TLS - the threat model each covers, a measured 1.2ms mTLS handshake that keep-alive erases, and why the real decision is operational, not performance.</description>
		</item>
		<item>
			<title>Rezee for agencies - a clean workspace per client, a clean handoff at the end</title>
			<link>https://rezee.app/blog/rezee-for-agencies</link>
			<guid>https://rezee.app/blog/rezee-for-agencies</guid>
			<pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
			<description>How development agencies run client work in Rezee - isolation between clients, the whole delivery record in one place, and handoffs where the client gets everything, not a zip file.</description>
		</item>
		<item>
			<title>Rezee for agent-forward teams - the workspace built for humans plus agents</title>
			<link>https://rezee.app/blog/rezee-for-agent-forward-teams</link>
			<guid>https://rezee.app/blog/rezee-for-agent-forward-teams</guid>
			<pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate>
			<description>How teams that develop with AI agents from day one run on Rezee - one permission model, full context for delegation, review as the human bottleneck solved structurally.</description>
		</item>
		<item>
			<title>The workspace is the context window - why agents work better unified</title>
			<link>https://rezee.app/blog/workspace-as-context-window</link>
			<guid>https://rezee.app/blog/workspace-as-context-window</guid>
			<pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate>
			<description>The engineering thesis behind Rezee's agent bet - an agent in a unified workspace gets context, permissions, identity, and a safety gate as properties of one system, each measured in a sibling post, where a stitched stack rebuilds all four per integration.</description>
		</item>
		<item>
			<title>One search across five surfaces - on Postgres, and when it falls over</title>
			<link>https://rezee.app/blog/unified-search-postgres-fts</link>
			<guid>https://rezee.app/blog/unified-search-postgres-fts</guid>
			<pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
			<description>How Rezee searches issues, docs, chat, PRs, and code paths with Postgres full-text search instead of a separate engine - measured GIN latency to 1,000,000 rows, the p99 tail that is the real fall-over signal, and why workspace-scoping keeps it flat.</description>
		</item>
		<item>
			<title>A ref named --output - defending a shell-out git API from option injection</title>
			<link>https://rezee.app/blog/git-api-option-injection</link>
			<guid>https://rezee.app/blog/git-api-option-injection</guid>
			<pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
			<description>How Rezee's git read layer stops a repository ref from becoming a git flag - the real arbitrary-file-write exploit, the two guards in denji's gitdata.go, a four-config attack matrix showing what each layer independently catches, and the one command where --end-of-options provides zero protection.</description>
		</item>
		<item>
			<title>A git SSH server in 300 lines, with the key database in another service</title>
			<link>https://rezee.app/blog/git-ssh-server-delegated-auth</link>
			<guid>https://rezee.app/blog/git-ssh-server-delegated-auth</guid>
			<pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
			<description>How Rezee serves git over SSH with delegated public-key auth - denji holds no keys, resolves fingerprints through makima, and runs stateful upload-pack (no --stateless-rpc) - plus the measured ref-advertisement cost that separates SSH from HTTP transport.</description>
		</item>
		<item>
			<title>Closes ACME-12 - parsing closing keywords without closing the wrong issue</title>
			<link>https://rezee.app/blog/issue-pr-autoclose-parsing</link>
			<guid>https://rezee.app/blog/issue-pr-autoclose-parsing</guid>
			<pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
			<description>How Rezee links a merged PR to the issue it closes by parsing closing keywords - tested against 500 real OSS pull requests, where the naive regex would have auto-closed the wrong issue from a code block, and the two corrections that stop it.</description>
		</item>
		<item>
			<title>Killing the 2-second poll - one SSE stream for the whole workspace</title>
			<link>https://rezee.app/blog/sse-vs-polling</link>
			<guid>https://rezee.app/blog/sse-vs-polling</guid>
			<pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
			<description>The engineering behind Rezee's real-time sync engine - measured costs of polling vs server-sent events (requests, wire bytes, staleness), the anatomy of an SSE stream, the proxy and connection-limit traps, and why writes stay REST.</description>
		</item>
		<item>
			<title>Scoped tokens - giving an agent the minimum, and proving it holds</title>
			<link>https://rezee.app/blog/scoped-tokens-for-agents</link>
			<guid>https://rezee.app/blog/scoped-tokens-for-agents</guid>
			<pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
			<description>How Rezee scopes agent access tokens to capability and resource - the scope grammar, the single matcher that gates every tool call, and a 200,000-pair adversarial fuzz proving zero privilege escalations against an independent oracle.</description>
		</item>
		<item>
			<title>Rezee for solo founders - a whole team's tooling for a team of one</title>
			<link>https://rezee.app/blog/rezee-for-solo-founders</link>
			<guid>https://rezee.app/blog/rezee-for-solo-founders</guid>
			<pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
			<description>How a solo technical founder runs specs, planning, code, CI, and AI agents in one workspace - why tool sprawl hurts most at n=1, and how agents become your first teammates.</description>
		</item>
		<item>
			<title>Rezee for 5-person startups - one workspace before the seams set in</title>
			<link>https://rezee.app/blog/rezee-for-small-startups</link>
			<guid>https://rezee.app/blog/rezee-for-small-startups</guid>
			<pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate>
			<description>How a small startup team runs its whole lifecycle in Rezee - the moment tool sprawl starts costing real money, the consolidation math, and onboarding a team without an onboarding doc.</description>
		</item>
		<item>
			<title>One tool surface for humans, agents, and MCP - generated, not maintained</title>
			<link>https://rezee.app/blog/one-tool-surface-mcp</link>
			<guid>https://rezee.app/blog/one-tool-surface-mcp</guid>
			<pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate>
			<description>How Rezee exposes the same API to its UI, external agents over MCP, and first-party agents - 65 MCP tools mechanically derived from the same TypeBox route schemas, so the tool an agent calls and the endpoint a human hits are the same code.</description>
		</item>
		<item>
			<title>The life of a CI log line (or - how &quot;live&quot; do live logs need to be?)</title>
			<link>https://rezee.app/blog/life-of-a-ci-log-line</link>
			<guid>https://rezee.app/blog/life-of-a-ci-log-line</guid>
			<pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
			<description>How a log line travels from a build container to your browser in Rezee - scanner, redaction, 20-line batches, one Postgres row per line, and 2-second polling - and why we chose boring over push.</description>
		</item>
		<item>
			<title>How encrypted secrets work in Rezee pipelines</title>
			<link>https://rezee.app/blog/how-pipeline-secrets-work</link>
			<guid>https://rezee.app/blog/how-pipeline-secrets-work</guid>
			<pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
			<description>The full path of a CI secret - AES-256-GCM at rest, names-only listing, decryption only at dispatch over an internal channel, Docker env injection that stays out of inspect, and log redaction with honest caveats.</description>
		</item>
		<item>
			<title>How we built a CI runner in Go (in about 500 lines)</title>
			<link>https://rezee.app/blog/building-a-ci-runner-in-go</link>
			<guid>https://rezee.app/blog/building-a-ci-runner-in-go</guid>
			<pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate>
			<description>The architecture of kobeni, Rezee's pipeline executor - Postgres as the job queue, optimistic claims, a throwaway Docker container per step, zipped artifacts, and the gaps we haven't filled yet.</description>
		</item>
		<item>
			<title>The post-receive hook is the event bus - one git push, measured end to end</title>
			<link>https://rezee.app/blog/post-receive-event-bus</link>
			<guid>https://rezee.app/blog/post-receive-event-bus</guid>
			<pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate>
			<description>How a git push in Rezee triggers pipelines and signed webhooks across two services with no message broker - the env-injected shell hook, fire-and-forget at every hop, and a measured 75-second push stall that the design's own honesty exposed.</description>
		</item>
		<item>
			<title>Keep the LLM loop out of the API - the beam agent runtime</title>
			<link>https://rezee.app/blog/beam-agent-runtime</link>
			<guid>https://rezee.app/blog/beam-agent-runtime</guid>
			<pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
			<description>Why Rezee runs agents in a separate worker service instead of inside the API - a measured 14x tail-latency blowup when the agent loop shares the request path, and the kobeni-shaped runtime that avoids it.</description>
		</item>
		<item>
			<title>The approval gate - how &quot;humans keep the final say&quot; works as a state machine</title>
			<link>https://rezee.app/blog/agent-approval-gate</link>
			<guid>https://rezee.app/blog/agent-approval-gate</guid>
			<pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
			<description>The engineering behind Rezee's agent approval gate - the agent_tasks state machine, why steps are append-only rows, the conditional UPDATE that makes double-approval impossible, and what happens when the runtime dies mid-task.</description>
		</item>
		<item>
			<title>Designing workspace-scoped multi-tenancy for a developer platform</title>
			<link>https://rezee.app/blog/workspace-scoped-multi-tenancy</link>
			<guid>https://rezee.app/blog/workspace-scoped-multi-tenancy</guid>
			<pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
			<description>How Rezee isolates workspaces on one Postgres - scoping by foreign key, revocable server-side sessions, hashed access tokens, and the single authorize endpoint that answers every git permission question.</description>
		</item>
		<item>
			<title>How we use Rezee to build Rezee</title>
			<link>https://rezee.app/blog/how-we-use-rezee-to-build-rezee</link>
			<guid>https://rezee.app/blog/how-we-use-rezee-to-build-rezee</guid>
			<pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate>
			<description>Dogfooding all the way down - how the Rezee team runs specs, planning, code, CI, and agents inside Rezee itself, what the naming scheme is about, and what building on your own product teaches you.</description>
		</item>
		<item>
			<title>The product development lifecycle in one place - a practical guide</title>
			<link>https://rezee.app/blog/product-development-lifecycle-guide</link>
			<guid>https://rezee.app/blog/product-development-lifecycle-guide</guid>
			<pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate>
			<description>A walkthrough of the full lifecycle - idea, spec, plan, build, review, ship, learn - with the handoffs where teams lose context, and how to run each stage so the next one inherits everything.</description>
		</item>
		<item>
			<title>How to onboard an AI agent as a teammate (and keep the final say)</title>
			<link>https://rezee.app/blog/onboarding-ai-agents</link>
			<guid>https://rezee.app/blog/onboarding-ai-agents</guid>
			<pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate>
			<description>A practical playbook for adding an AI agent to a software team - choosing first tasks, scoping permissions, setting review gates, and growing trust in stages without losing human control.</description>
		</item>
		<item>
			<title>Docs that don't rot - keeping engineering knowledge next to the code</title>
			<link>https://rezee.app/blog/docs-that-dont-rot</link>
			<guid>https://rezee.app/blog/docs-that-dont-rot</guid>
			<pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate>
			<description>Why engineering documentation decays, which docs are worth writing at all, and the structural habits - ownership, proximity, and living status - that keep knowledge truthful.</description>
		</item>
		<item>
			<title>Rezee vs Notion + Slack - where should an engineering team's knowledge and conversation live?</title>
			<link>https://rezee.app/blog/rezee-vs-notion-and-slack</link>
			<guid>https://rezee.app/blog/rezee-vs-notion-and-slack</guid>
			<pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
			<description>Notion holds the docs, Slack holds the conversation, and neither knows what the code is doing. An honest comparison with Rezee's model, where docs and chat share a workspace with the work itself.</description>
		</item>
		<item>
			<title>Rezee vs Linear + GitHub - do planning and code belong in separate tools?</title>
			<link>https://rezee.app/blog/rezee-vs-linear-and-github</link>
			<guid>https://rezee.app/blog/rezee-vs-linear-and-github</guid>
			<pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate>
			<description>Linear plus GitHub is the modern startup default - a great planner synced to a great code host. An honest look at what that pairing does well, where the sync model leaks, and when one workspace is the better answer.</description>
		</item>
		<item>
			<title>What context switching actually costs your engineering team</title>
			<link>https://rezee.app/blog/cost-of-context-switching</link>
			<guid>https://rezee.app/blog/cost-of-context-switching</guid>
			<pubDate>Thu, 16 Apr 2026 00:00:00 GMT</pubDate>
			<description>The research on interruption and attention residue, translated into engineering terms - what tab-hopping between code, tracker, chat, and docs really costs, and what actually reduces it.</description>
		</item>
		<item>
			<title>The best all-in-one developer platforms in 2026</title>
			<link>https://rezee.app/blog/best-all-in-one-developer-platforms</link>
			<guid>https://rezee.app/blog/best-all-in-one-developer-platforms</guid>
			<pubDate>Fri, 10 Apr 2026 00:00:00 GMT</pubDate>
			<description>A fair guide to the platforms that unify code, planning, CI/CD, and more - GitLab, Atlassian, Gitea and Forgejo, OneDev, and Rezee - with honest strengths, gaps, and who each one actually fits.</description>
		</item>
		<item>
			<title>Rezee vs GitHub - when a unified workspace beats a code-first platform</title>
			<link>https://rezee.app/blog/rezee-vs-github</link>
			<guid>https://rezee.app/blog/rezee-vs-github</guid>
			<pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate>
			<description>GitHub is the default home for code. Rezee is a workspace for the whole lifecycle - code, planning, CI/CD, chat, and docs. An honest comparison for teams deciding where their work should live.</description>
		</item>
		<item>
			<title>What your team actually pays for GitHub + Linear + Slack + Notion + CI</title>
			<link>https://rezee.app/blog/what-your-dev-stack-actually-costs</link>
			<guid>https://rezee.app/blog/what-your-dev-stack-actually-costs</guid>
			<pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate>
			<description>The real monthly cost of the standard startup dev stack - subscription math for a 10-person team, plus the hidden costs of seams - and an honest look at when consolidation pays.</description>
		</item>
		<item>
			<title>Our job queue is one Postgres UPDATE - so we raced it until it broke</title>
			<link>https://rezee.app/blog/postgres-job-queue-one-update</link>
			<guid>https://rezee.app/blog/postgres-job-queue-one-update</guid>
			<pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate>
			<description>We benchmarked the atomic claim behind Rezee's CI queue against the naive version and FOR UPDATE SKIP LOCKED - 100 concurrent workers, 10,000 jobs, real numbers on duplicates, wasted claims, latency, and the surprising way a guarded queue slows down under contention.</description>
		</item>
		<item>
			<title>How small teams should structure issues, labels, and workflows</title>
			<link>https://rezee.app/blog/issue-tracking-for-small-teams</link>
			<guid>https://rezee.app/blog/issue-tracking-for-small-teams</guid>
			<pubDate>Fri, 27 Mar 2026 00:00:00 GMT</pubDate>
			<description>A minimal issue-tracking setup that stays truthful - what states you actually need, which labels earn their keep, how big an issue should be, and the habits that prevent tracker rot.</description>
		</item>
		<item>
			<title>Code review best practices - reviews that don't slow the team down</title>
			<link>https://rezee.app/blog/code-review-best-practices</link>
			<guid>https://rezee.app/blog/code-review-best-practices</guid>
			<pubDate>Thu, 26 Mar 2026 00:00:00 GMT</pubDate>
			<description>How to keep code review fast and useful at the same time - small PRs, clear review levels, latency norms, and what reviewers should actually look for (and skip).</description>
		</item>
		<item>
			<title>Spec to issues to shipped - how to keep planning and code in sync</title>
			<link>https://rezee.app/blog/spec-to-shipped</link>
			<guid>https://rezee.app/blog/spec-to-shipped</guid>
			<pubDate>Mon, 23 Mar 2026 00:00:00 GMT</pubDate>
			<description>Why trackers drift from reality, how to link issues to pull requests so status maintains itself, and the closed-loop workflow that keeps a spec truthful from first draft to deploy.</description>
		</item>
		<item>
			<title>Agents are just users - the one schema decision that made every surface agent-ready</title>
			<link>https://rezee.app/blog/agents-are-just-users</link>
			<guid>https://rezee.app/blog/agents-are-just-users</guid>
			<pubDate>Tue, 17 Mar 2026 00:00:00 GMT</pubDate>
			<description>How Rezee made AI agents first-class teammates with a single enum column - 15 existing foreign keys that worked on day one, the two columns that fought back, and the measured cost of the polymorphic alternative we didn't pick.</description>
		</item>
		<item>
			<title>Why Rezee runs on Go, Bun, and React</title>
			<link>https://rezee.app/blog/why-go-bun-and-react</link>
			<guid>https://rezee.app/blog/why-go-bun-and-react</guid>
			<pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
			<description>The reasoning behind Rezee's polyglot stack - Go for the git engine and CI executor, Bun and ElysiaJS for the API, React with TanStack for the UI - and the seams between them.</description>
		</item>
		<item>
			<title>How we built a git server in Go (without reimplementing git)</title>
			<link>https://rezee.app/blog/building-a-git-server-in-go</link>
			<guid>https://rezee.app/blog/building-a-git-server-in-go</guid>
			<pubDate>Thu, 12 Mar 2026 00:00:00 GMT</pubDate>
			<description>The architecture of denji, the git engine behind Rezee - smart HTTP and SSH transports in ~2,000 lines of Go, one dependency, and the git binary doing what it does best.</description>
		</item>
		<item>
			<title>Rezee vs the Atlassian stack - Jira, Bitbucket, and Confluence, or one workspace?</title>
			<link>https://rezee.app/blog/rezee-vs-atlassian</link>
			<guid>https://rezee.app/blog/rezee-vs-atlassian</guid>
			<pubDate>Fri, 06 Mar 2026 00:00:00 GMT</pubDate>
			<description>Atlassian assembled the enterprise standard - Jira for planning, Bitbucket for code, Confluence for docs. An honest comparison with Rezee's single-workspace model, and who each is really for.</description>
		</item>
		<item>
			<title>A beginner's guide to CI/CD pipelines in YAML</title>
			<link>https://rezee.app/blog/ci-cd-pipelines-yaml-guide</link>
			<guid>https://rezee.app/blog/ci-cd-pipelines-yaml-guide</guid>
			<pubDate>Wed, 04 Mar 2026 00:00:00 GMT</pubDate>
			<description>What CI/CD actually does, how to read and write pipeline YAML - jobs, steps, dependencies, artifacts, secrets - and the habits that keep pipelines fast and trustworthy.</description>
		</item>
		<item>
			<title>The best tools for teams working with AI coding agents in 2026</title>
			<link>https://rezee.app/blog/best-tools-for-ai-agent-teams</link>
			<guid>https://rezee.app/blog/best-tools-for-ai-agent-teams</guid>
			<pubDate>Tue, 03 Mar 2026 00:00:00 GMT</pubDate>
			<description>A practical guide to the agent-era stack - coding agents, review tooling, CI, and the workspace layer that gives agents context and guardrails - with honest notes on what each piece solves.</description>
		</item>
		<item>
			<title>Rezee vs GitLab - two takes on all-in-one</title>
			<link>https://rezee.app/blog/rezee-vs-gitlab</link>
			<guid>https://rezee.app/blog/rezee-vs-gitlab</guid>
			<pubDate>Wed, 25 Feb 2026 00:00:00 GMT</pubDate>
			<description>GitLab unified the DevOps toolchain. Rezee unifies the product development lifecycle - including chat, docs, and AI agents. An honest comparison of scope, strengths, pricing, and when to pick each.</description>
		</item>
		<item>
			<title>How to write an RFC that actually gets read (with template)</title>
			<link>https://rezee.app/blog/how-to-write-an-rfc</link>
			<guid>https://rezee.app/blog/how-to-write-an-rfc</guid>
			<pubDate>Fri, 20 Feb 2026 00:00:00 GMT</pubDate>
			<description>A practical guide to writing engineering RFCs - what to include, what to cut, how to route them for review, and a copy-paste template your team can adopt today.</description>
		</item>
		<item>
			<title>Why we built Rezee - the case against seven SaaS tabs</title>
			<link>https://rezee.app/blog/why-we-built-rezee</link>
			<guid>https://rezee.app/blog/why-we-built-rezee</guid>
			<pubDate>Thu, 19 Feb 2026 00:00:00 GMT</pubDate>
			<description>Product development is scattered across code hosting, issue tracking, CI, chat, and docs that never quite agree. Rezee is our answer - one workspace for the whole lifecycle, built for teams and their AI agents.</description>
		</item>
		<item>
			<title>Introducing the Rezee blog</title>
			<link>https://rezee.app/blog/introducing-the-rezee-blog</link>
			<guid>https://rezee.app/blog/introducing-the-rezee-blog</guid>
			<pubDate>Mon, 16 Feb 2026 00:00:00 GMT</pubDate>
			<description>What we'll write about here - practical guides on shipping software, engineering deep-dives on how Rezee is built, honest tool comparisons, and notes on the product itself.</description>
		</item>
</channel></rss>
