A large automation plan hides the basic question: can this setup deliver useful work?
A small, complete workflow demonstrates what works and what needs adjustment.
1. Prepare the execution environment
Configure your Norc instance and the agent execution path you will use. For Claude Code or Codex, install and authenticate the CLI on the machine that runs it, then connect its runner.
Verify that the environment has the required repository and tools. The underlying provider account and infrastructure are separate from Norc. Use the project documentation for installation details that match your deployment.
2. Define the project and access
Create a project with a concrete goal and relevant knowledge. Add a task with scope, acceptance checks, and expected evidence. Enable the skills you want the agent to use and assign only the credentials needed for the work.
Set a project budget, a per-run cap, working hours, and an autonomy policy suitable for a first run. Keep the first task small enough that you can inspect both the process and the result.
3. Run one task and review what came back
Observe the run, inspect its transcript if it goes off course, and steer or stop it when appropriate. Review the artifact and checks against the brief. Record missing context or unclear instructions before starting another task.
When a single task works well, add a dependent task that uses its output. This tests the handoff before you expand concurrency or introduce more agent roles.
Decide what to expand next
Evaluate accepted output, review effort, recorded cost, and coordination time. If you are spending most of your time correcting the brief, improve the context before adding agents.
If a repeatable workflow is producing useful results, consider more tasks, additional roles, or greater autonomy. Expansion should follow observed results rather than the number of agents you can connect.
Practical questions.
Where do I start the setup?
Use Start using Norc to open config.getnorc.com. The repository documentation also describes installation and runner requirements.
Do I need an external task board?
No. Norc includes a native Mission Board. Connect an external tracker only when it helps your existing workflow.
By the Norc team · Product details checked against the Norc project documentation. View the project