Start using Norc
YOUR AGENTS. FINALLY A TEAM.

More work done.Less workmanaging AI.

Norc coordinates your AI agents, carries context between tasks, and brings results back for review. You set the direction.

Start using Norc
Bring the agents you already use.
Claude CodeCodex+ more
INSIDE YOUR NEXT WORKDAY01 — 04
?“What’s the context?”
↗“Who takes this next?”
↻“Is this finished?”
Ready for the task
Launch customer export
Project contextRelevant skillsAssigned secrets
✓ Supplied automatically per run
Claude CodeBuild
CodexTest
✓Next task, ready.
✓Ready for your review
Customer export

Code, tests, and a clear summary.

You make the final call.↗
You · Set the direction.
ILLUSTRATIVE WORKFLOW
Without Norc, every handoff comes back to you.
BUILT AROUND YOUR EXISTING WORK.

Keep your agents.
Connect the work around them.

Claude CodeCodexGitHubLinearNotionSlack
Supported tools · connect what you need
FROM THE IDEA TO THE ACTUAL WORK.

Here’s what working
with Norc looks like.

Follow one customer request through the workspace.
The brief, the handoffs, and the result — all connected.

01Give the work a home

One brief. A team that knows the project.

Add project context, enable skills, and assign credentials. Norc supplies relevant skills and each agent’s assigned secrets at run time, alongside the brief and past results.

Less re-explaining. Less agent-by-agent setup.

Skills follow your configuration. Vault secrets can be assigned to specific agents or shared across your team.

norc.Acme workspace Customer exportJD
PROJECT / OVERVIEW

Customer export

Active project

Let customers take their data with them.

SHARED CONTEXT

Build CSV export for customer records. Respect existing permissions. Include empty states and tests.

Product briefacme / appEnabled skills
PROJECT TEAM
Claude CodeImplementation
CodexTesting & review
Context and skills travel with the task.
Product illustration · example data01 / 03
02Move work through the team

A handoff shouldn’t become another job.

Define the tasks and what depends on what. Norc routes work to available agents and starts eligible follow-up tasks when their dependencies finish.

Keep delivery moving between individual tasks.

Automatic starts follow your project’s autonomy policy. You can also assign and run tasks yourself.

norc.Acme workspace Customer exportJD
WORK / MISSION BOARD

From brief to delivery

3 tasks

One project. Clear ownership. Connected steps.

NOR-142Build customer CSV exportClaude Code
Done
Implementation finished → tests can start
NOR-143Test export permissionsCodex
Running
NOR-144Update export documentationClaude Code
Queued
Dependencies carry the result into the next task.
Product illustration · example data02 / 03
03Review something concrete

See the work. Then make the call.

Open a run to see the conversation, context, cost, and result. For coding work, inspect the branch, commits, and changes before deciding what ships.

Less checking tabs. More informed decisions.

A morning digest brings owners the work that finished and the decisions still waiting.

norc.Acme workspace Customer exportJD
WORK / RUNS / NOR-142

Customer CSV export

Completed
Claude CodeResult attached
AGENT SUMMARY

Added CSV export with permission checks, empty-state handling, and tests.

norc/customer-export+124−18
Changes3 files
Test resultsAttached
Conversation & contextRecorded
The run finished. You decide what ships.Review the evidence before merging or releasing.
Product illustration · example data03 / 03
norc.Acme workspace Customer exportJD
PROJECT / OVERVIEW

Customer export

Active project

Let customers take their data with them.

SHARED CONTEXT

Build CSV export for customer records. Respect existing permissions. Include empty states and tests.

Product briefacme / appEnabled skills
PROJECT TEAM
Claude CodeImplementation
CodexTesting & review
Context and skills travel with the task.
Product illustration · example data01 / 03
WHY ADD NORC TO YOUR TEAM?

Keep the agents you trust.
Give them a way to work together.

Your agents handle individual tasks. Norc handles the coordination around them — so the whole project can move forward.

01
You repeat the brief.

Context follows the work.

Project goals, knowledge, and previous results go with the task. Your team starts with the same understanding.

02
You move every handoff.

The team keeps moving.

Tasks reach the right agent. Dependencies connect the steps. Configured backups help when an agent gets stuck.

03
You check every tab.

You see what needs you.

One place for live progress, costs, and reviewable results. Set budgets and approval rules before work begins.

DELEGATION WITH BOUNDARIES.

Give your team room to work.
Keep the decisions that matter.

More autonomy should come with more visibility.
Set the rules, follow live runs, and steer or stop when needed.

Put a boundary around spend.

Set monthly project budgets and per-run caps. Get an alert at 80%; project execution pauses at the budget limit.

Customer export / Project rulesEXAMPLE
MONTHLY PROJECT BUDGET
$180 / $30060% used
$0Alert at 80%Pause at 100%
Per-run cap$15
Budget alertsProject owners

Illustrative limits and usage, not Norc pricing.

Run coding agents on machines you connect.

Connect a local machine or a shared server through a Norc runner. Isolated git workspaces keep parallel coding tasks separate.

Read the setup guide
START SMALL. MAKE IT USEFUL.

Your first project,
not a company-wide rollout.

Best for product teams, agencies, and founders already using AI agents to deliver work.

  1. 01

    Choose one bounded piece of work.

    A feature, a bug fix, or a client deliverable with a clear definition of done.

  2. 02

    Connect the team and set the rules.

    Add a runner and your agents. Bring the project context, then choose budgets and autonomy.

  3. 03

    Review the first result. Build from there.

    Start manually, inspect the output, and expand once the workflow works for you.

LESS CHASING. MORE DELIVERING.

A team that moves work.
Room for you to lead.

Bring one project and the agents you already use.
Give them direction. See what comes back.

Start using Norc Your agents. Your rules. Your call.
CLEAR BEFORE YOU START.

A few practical questions.

How is this different from using Claude Code or Codex?

Those agents do the work. Norc coordinates the team around them: shared project context, task routing, dependencies, budgets, and results in one place. You can use multiple supported agents without personally carrying every handoff.

Who is Norc built for?

Product teams, agencies, and founders already using AI agents to deliver work. Start with one real project and clearly defined tasks, then expand after reviewing the results.

Can I keep my tools and stay in control?

Yes. Bring Claude Code, Codex, and other supported agents. Connect tools including Notion, GitHub, Linear, and Slack as needed. You decide working hours, budgets, and autonomy rules, and can steer or stop a run.

What do I need to get started?

A Norc instance, a project, and a supported agent. For Claude Code or Codex, connect a runner on a machine where the CLI is installed and authenticated. Add your context and start a clearly scoped task. Notion is optional; Norc has its own Mission Board.

What if an agent is wrong or gets stuck?

AI output still needs review. Norc exposes run context, conversation, and evidence so you can inspect it. Thin briefs can be sent back for clarification. For blocked agents, configure a stand-in, wait-and-retry behavior, or a human decision; recovery does not guarantee a correct result.

Does Norc replace my agent subscriptions?

No. Norc coordinates the agents you connect. Their subscriptions or API usage, and the infrastructure where they run, remain separate. Project budgets help you manage recorded run costs; they are not a promise that third-party charges disappear.

A CLEARER WAY TO START

Make it work for your team.

Understand the workflow. Prepare one good task. See what comes back.

How agent orchestration works How context, skills, and access reach a run Set up your first project